# How to connect Kit to OpenClaw (no API keys) > 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. Web version: https://claw-link.dev/openclaw/kit 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. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/kit ## Setup It takes three steps to connect OpenClaw to Kit. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Kit** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect kit # connect Kit (browser OAuth) npx -y @useclawlink/cli actions kit # list available actions npx -y @useclawlink/cli run kit --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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](https://claw-link.dev/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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/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](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Kit integration](https://claw-link.dev/hermes/kit) 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 | ## Example prompts **Create Broadcast** > Create it in Kit for me, then confirm the important fields before you finish. **Create Custom Field** > Create it in Kit for me, then confirm the important fields before you finish. **Create Subscriber** > Create it in Kit for me, then confirm the important fields before you finish. **Create Tag** > 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### 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. ### 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. ## Related - [OpenClaw ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences