# How to connect Customer.io to OpenClaw (paste one key, 23 tools) > Connect Customer.io to OpenClaw with ClawLink: paste your Customer.io key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/customerio The usual route to Customer.io 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 Customer.io setup: install one ClawHub skill, connect Customer.io in the browser, and OpenClaw can call real Customer.io actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Customer.io. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Customer.io** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 customerio # connect Customer.io (browser OAuth) npx -y @useclawlink/cli actions customerio # list available actions npx -y @useclawlink/cli run customerio --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 Customer.io in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Customer.io API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Customer.io, summarize it in plain English, and point out anything that needs attention. ### 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 Customer.io is connected in the dashboard, that agent calls the same 23 Customer.io 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). ## Customer.io MCP for OpenClaw Looking for a Customer.io MCP server for OpenClaw? ClawLink connects Customer.io to OpenClaw and exposes 23 Customer.io 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 Customer.io integration](https://claw-link.dev/hermes/customerio) works the same way. ## What the OpenClaw Customer.io integration can do 23 Customer.io tools are ready for OpenClaw once the account is connected. ### All 23 Customer.io tools for OpenClaw | Tool | What it does | |---|---| | **Get integrations** `customerio_get_integrations` | Retrieve a list of integrations in your workspace | | **Get messages** `customerio_get_messages` | Retrieve a list of messages sent from your workspace | | **Get segment details** `customerio_get_segment_details` | Retrieve details of a specific segment | | **Get segment membership** `customerio_get_segment_membership` | Retrieve people in a specific segment | | **Get segments** `customerio_get_segments` | Retrieve a list of segments in your workspace | | **Get trigger** `customerio_get_trigger` | Retrieves details about a specific API-triggered broadcast, including trigger ID, campaign ID | | **Get triggers** `customerio_get_triggers` | Retrieve all API trigger instances for a specific broadcast/campaign | | **Get webhooks** `customerio_get_webhooks` | Retrieves all reporting webhook configurations from the Customer.io workspace | | **List collections** `customerio_list_collections` | List all Collections metadata | | **List ip addresses** `customerio_list_ip_addresses` | Retrieve the list of IP addresses used by Customer.io for sending messages | | **List newsletters** `customerio_list_newsletters` | List all newsletters | | **List snippets** `customerio_list_snippets` | List all snippets in your workspace | | **List transactional messages** `customerio_list_transactional_messages` | Lists all transactional message templates in your Customer.io workspace | | **Add person to group** `customerio_add_person_to_group` | Add people to a group in Customer.io | | **Create alias** `customerio_create_alias` | Create an alias to merge multiple profiles in Customer.io | | **Identify person** `customerio_identify_person` | Identify a person and assign traits to them in Customer.io | | **Send batch** `customerio_send_batch` | Send multiple CDP calls (identify, track, page, screen, group, alias) in a single batch request | | **Track event** `customerio_track_event` | Send an event associated with a person in Customer.io | | **Track page** `customerio_track_page` | Track page view events for website visitors in Customer.io | | **Track screen** `customerio_track_screen` | Track mobile screen views in Customer.io for analytics and user journey tracking | | **Trigger broadcast** `customerio_trigger_broadcast` | Manually trigger a Customer.io broadcast/campaign to send messages to a defined audience | | **Customer io suppress person** `customerio_customer_io_suppress_person` | Suppress a customer profile to permanently delete it and prevent re-adding with the same | | **Unsubscribe delivery** `customerio_unsubscribe_delivery` | Handle custom unsubscribe requests for email deliveries in Customer.io | ## Example prompts **Get Integrations** > Pull the relevant data from Customer.io, summarize it in plain English, and point out anything that needs attention. **Get Messages** > Pull the relevant data from Customer.io, summarize it in plain English, and point out anything that needs attention. **Get Segment Details** > Pull the relevant data from Customer.io, summarize it in plain English, and point out anything that needs attention. **Get Segment Membership** > Pull the relevant data from Customer.io, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 Customer.io working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Customer.io API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Customer.io account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Customer.io. | 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 Customer.io actions to the runtime in a format your agent can reliably use. | 23 tools for Customer.io are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Customer.io 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 Customer.io in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the Customer.io key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Customer.io skill but can't call the tools The ClawHub skill teaches OpenClaw about Customer.io, but the calls run through the ClawLink plugin and your connected account. Make sure Customer.io 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 Customer.io 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 Customer.io tools Customer.io 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 Customer.io 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. ### Customer.io 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. ### API key setup works but results look incomplete Double-check that the API key for Customer.io has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Customer.io integration? Yes. ClawLink is the fastest way to connect OpenClaw to Customer.io: link your Customer.io account once in the browser and OpenClaw can call the Customer.io API through 23 ready-made tools — no custom code or token handling. ### How do I add Customer.io to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Customer.io skill from ClawHub, then you click Connect in the dashboard to authorize Customer.io. OpenClaw calls the tools from the next message — no config files, and the Customer.io key you paste is stored server-side instead of in your environment. ### How long does it take to connect Customer.io to OpenClaw? About two minutes. Sign in, click Connect next to Customer.io in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Customer.io up myself? The alternative to ClawLink is usually manual API key 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 Customer.io working from chat. ### OpenClaw installed the Customer.io skill but can't call the tools The ClawHub skill teaches OpenClaw about Customer.io, but the calls run through the ClawLink plugin and your connected account. Make sure Customer.io 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 - [ActiveCampaign tools](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email tools](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences