Keap
Keap (formerly Infusionsoft) CRM: contacts, tags, companies, opportunities, tasks, notes, campaigns, orders and transactional email over the Keap REST v2 API.
About
Keap ships in the w6w first-party pack. It declares 36 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.keap- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Marketing · Email
Overview
Keap (formerly Infusionsoft) is a small-business CRM and marketing-automation platform, and this app covers the parts a workflow actually reaches for: contacts, tags, companies, opportunities, tasks, notes, campaigns, automations, commerce reads, users, and transactional email.
On the contact side, it handles the full lifecycle — creating, updating and tagging contacts, attaching notes, and looking up a contact’s applied tags — alongside company and opportunity tracking through Keap’s pipeline stages. It can add contacts to a campaign sequence, trigger an automation goal, and send transactional email through Keap’s own delivery. Commerce data — products, orders and subscriptions — is available to read, so a workflow can act on purchase history without a separate billing integration.
Appointments are included as a small addition for scheduling-adjacent workflows. Health checks track daily and per-minute quota headroom across Keap’s own usage tiers and the shared tenant ceiling, plus Keap’s status page, so a workflow can tell its own throttling apart from someone else’s traffic on the same account.
Build with Keap
Three routes to the same 36 actions. The Workflow tab is generated from Keap's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Appointment
appointment-create Create a calendar appointment, optionally attached to a contact with a pop-up reminder. Uses Keap's v1 API — v2 has no appointment endpoints.
List Appointments
appointment-list List appointments in a date window, optionally for one contact. Uses Keap's v1 API — v2 has no appointment endpoints at all.
Achieve Automation Goal
automation-goal-achieve Fire an API goal for one contact, starting or stopping the campaign sequences behind it.
Get Business Profile
business-profile-get Read the connected Keap account's business profile: name, contact details, address, time zone, currency and branding.
List Campaigns
campaign-list List marketing campaigns, with their active and completed contact counts.
Add Contacts to Campaign Sequence
campaign-sequence-add-contacts Start a batch of contacts on a published campaign sequence, reporting the outcome per contact.
List Campaign Sequences
campaign-sequence-list List the published sequences inside a campaign, with their contact counts.
Create Contact
contact-create Create a contact, or update the matching one when a duplicate-check strategy is chosen.
List Contacts
contact-list Search contacts by email, name, company, id or last-update window, using Keap's filter expression grammar.
List Contact Tags
contact-tags-list List the tags applied to a contact, with the time each was applied.
Update Contact
contact-update Update a contact. Only the properties you fill in are touched — an update mask is always sent, because Keap otherwise clears collection properties you omit.
Send Email
email-send Queue a one-off email to a batch of contacts, from a Keap user or a verified sender address.
Get Email Address Status
email-status-get Read one email address's opt-in status and last open, click and send times.
Create Opportunity
opportunity-create Create an opportunity against a contact, in a named pipeline stage.
List Subscriptions
subscription-list Search recurring billing subscriptions by contact, plan or status.
Apply Tag to Contacts
tag-apply Apply one tag to up to a batch of contacts, reporting the outcome per contact.
List Contacts with Tag
tag-contacts-list List the contacts carrying a tag, with the time it was applied to each.
List Users
user-list List the Keap users on the account — the source of the ids tasks, notes and emails are attributed to.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Keap's real ids.
{
"manifestVersion": "2",
"name": "keap-example",
"steps": [
{
"id": "appointment-create",
"uses": {
"app": "io.w6w.keap",
"action": "appointment-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"title": "<title>",
"startDate": "<startDate>",
"endDate": "<endDate>"
}
}
]
}Here are some of the things you can do
-
Create Appointment
performappointment-create -
List Appointments
searchappointment-list -
Achieve Automation Goal
performautomation-goal-achieve -
Get Business Profile
readbusiness-profile-get -
List Campaigns
searchcampaign-list
+31 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Keap, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Keap. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "contact-create",
payload: {
// givenName: "<value>",
// familyName: "<value>",
// email: "<value>",
// emailField: "<value>",
// phone: "<value>",
// phoneField: "<value>",
// companyId: "<value>",
// jobTitle: "<value>",
// ownerId: "<value>",
// leadsourceId: "<value>",
// contactType: "<value>",
// addresses: "<value>",
// customFields: "<value>",
// extra: "<value>",
// duplicateOption: "<value>",
// fields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action contact-create --payload '{}'Give an AI agent Keap — without giving it Keap's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.keap#appointment-create",
"input": {
"title": "<title>",
"startDate": "<startDate>",
"endDate": "<endDate>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Keap connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Keap's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Keap itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Keap declares its own checks, so its health is a property of the app rather than something the host guesses at.
Keap platform status
The Keap group on Thryv's status page — Authentication, APIs, Automation, Contacts/Company, Email, Forms, Landing Page and Communication. Thryv's other products share the page and are deliberately excluded from the verdict.
Throttle and quota headroom
Per-credential daily quota and per-minute throttle, plus the per-tenant ceiling shared with every other integration on the same Keap app, read from the x-keap-* headers on a single identity request.