How to connect Kit to OpenClaw
Connect Kit to OpenClaw with ClawLink in one click — 42 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
KitOAUTH2MCPEmail marketing and audience growth for creators. Once connected, OpenClaw can read and act on Kit from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Kit access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Kit setup: install one ClawHub skill, connect Kit in the browser, and OpenClaw can call real Kit actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Kit skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Kit" (hith3sh/kit-email-marketing) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/kit-email-marketing
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Kit.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Kit
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Kit?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Kit in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Create it in Kit for me, then confirm the important fields before you finish.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Kit is connected in the dashboard, that agent calls the same 42 Kit tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Kit MCP for OpenClaw
Looking for a Kit MCP server for OpenClaw? ClawLink connects Kit to OpenClaw and exposes 42 Kit tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Kit integration works the same way.
What the OpenClaw Kit integration can do
42 Kit tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 42.
30 of 42 Kit tools for OpenClaw
| Tool | What it does |
|---|---|
Create broadcast kit_create_broadcast | Create a Kit broadcast |
Create custom field kit_create_custom_field | Create a Kit custom field |
Create subscriber kit_create_subscriber | Create a Kit subscriber |
Create tag kit_create_tag | Create a Kit tag |
Filter subscribers kit_filter_subscribers | Filter Kit subscribers |
Get account kit_get_account | Get the connected Kit account |
Get broadcast kit_get_broadcast | Get a Kit broadcast by ID |
Get broadcast stats kit_get_broadcast_stats | Get Kit broadcast statistics |
Get email stats kit_get_email_stats | Get Kit email statistics |
Get growth stats kit_get_growth_stats | Get Kit growth statistics |
Get subscriber kit_get_subscriber | Get a Kit subscriber by ID |
List broadcasts kit_list_broadcasts | List Kit broadcasts |
List custom fields kit_list_custom_fields | List Kit custom fields |
List forms kit_list_forms | List Kit forms |
List tags kit_list_tags | List Kit tags |
Get account colors kit_get_account_colors | Retrieve list of colors associated with the account |
Get broadcast clicks kit_get_broadcast_clicks | Retrieve link click data for a specific broadcast by ID |
Get creator profile kit_get_creator_profile | Retrieve the creator profile information for the account |
Get subscriber stats kit_get_subscriber_stats | Retrieve email stats for a specific subscriber |
List email templates kit_list_email_templates | Retrieve a paginated list of all email templates in the Kit account |
List segments kit_list_segments | Retrieve a paginated list of segments |
List sequences kit_list_sequences | Retrieve a paginated list of all sequences |
List subscribers kit_list_subscribers | Retrieve a list of subscribers |
List subscribers for form kit_list_subscribers_for_form | Retrieves subscribers for a specific form by ID with optional filtering and cursor-based |
List tag subscribers kit_list_tag_subscribers | Retrieve subscribers for a specific tag |
List webhooks kit_list_webhooks | Retrieve a paginated list of all webhooks configured in the Kit account |
Add subscriber to form kit_add_subscriber_to_form | Add an existing subscriber to a form by their IDs |
Add subscriber to form by email kit_add_subscriber_to_form_by_email | Add an existing subscriber to a form using their email address |
Create webhook kit_create_webhook | Creates a webhook subscription for real-time event notifications |
Tag subscriber kit_tag_subscriber | Associate a subscriber with a specific tag by ID |
Try it: find the Kit tool you need
Browse the 30 Kit tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Kit for me, then confirm the important fields before you finish.
Create it in Kit for me, then confirm the important fields before you finish.
Create it in Kit for me, then confirm the important fields before you finish.
Create it in Kit for me, then confirm the important fields before you finish.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Kit working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Kit app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Kit through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Kit. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Kit actions to the runtime in a format your agent can reliably use. | 42 tools for Kit are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Kit to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Kit in the browser, and the 42 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Kit skill but can't call the tools
The ClawHub skill teaches OpenClaw about Kit, but the calls run through the ClawLink plugin and your connected account. Make sure Kit is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Kit from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Kit tools
Kit tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Kit call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Kit returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Kit and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Kit integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Kit: link your Kit account once in the browser and OpenClaw can call the Kit API through 42 ready-made tools — no custom code or token handling.
How do I add Kit to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Kit skill from ClawHub, then you click Connect in the dashboard to authorize Kit. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Kit to OpenClaw?
About two minutes. Sign in, click Connect next to Kit in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Kit up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Kit working from chat.
OpenClaw installed the Kit skill but can't call the tools
The ClawHub skill teaches OpenClaw about Kit, but the calls run through the ClawLink plugin and your connected account. Make sure Kit is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
