How to connect Iterable to OpenClaw
Connect Iterable to OpenClaw with ClawLink: paste your Iterable key once and 116 tools work from chat. No MCP server to run, nothing stored on your machine.
IterableAPI KEYMCPCreate, send, and track cross-channel marketing campaigns. Once connected, OpenClaw can read and act on Iterable from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Iterable 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 Iterable setup: install one ClawHub skill, connect Iterable in the browser, and OpenClaw can call real Iterable 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 Iterable.
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 Iterable
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Iterable?"
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 Iterable in the ClawLink dashboard — paste your Iterable API key once.
Verify the connection by asking OpenClaw:
Use Iterable to export data csv and walk me through the result in plain English.
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 Iterable is connected in the dashboard, that agent calls the same 116 Iterable tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Iterable MCP for OpenClaw
Looking for a Iterable MCP server for OpenClaw? ClawLink connects Iterable to OpenClaw and exposes 116 Iterable tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Iterable integration works the same way.
What the OpenClaw Iterable integration can do
116 Iterable 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 116.
30 of 116 Iterable tools for OpenClaw
| Tool | What it does |
|---|---|
Export data CSV iterable_export_data_csv | Export campaign analytics data in CSV format from Iterable |
Export data json iterable_export_data_json | Export campaign analytics data in JSON format with one entry per line |
Export user events iterable_export_user_events | Export all events for a user identified by email or userId |
Get campaign iterable_get_campaign | Retrieves a campaign by its unique ID |
Get campaign metrics iterable_get_campaign_metrics | Retrieve performance metrics for one or more campaigns |
Get catalog field mappings iterable_get_catalog_field_mappings | Retrieve field mappings (field to data type) and undefined fields for a catalog in Iterable |
Get catalog item iterable_get_catalog_item | Retrieves a specific catalog item by its ID from the specified catalog |
Get email template iterable_get_email_template | Get an email template by templateId |
Get embedded messages iterable_get_embedded_messages | Retrieves embedded messages for which the specified user is eligible, grouped by placementId |
Get embedded template iterable_get_embedded_template | Retrieves an embedded message template by its unique ID |
Get experiment metrics iterable_get_experiment_metrics | Retrieve metrics for email experiments |
Get in app messages iterable_get_in_app_messages | Get a user's in-app messages from Iterable |
Get in app template iterable_get_in_app_template | Retrieves an in-app template by its unique ID |
Get list size iterable_get_list_size | Get the number of users within a list |
Get push template iterable_get_push_template | Retrieves a push template by its unique ID |
Get sms template iterable_get_sms_template | Retrieves an SMS template by its unique ID |
Get snippet iterable_get_snippet | Retrieves a snippet by its ID (numeric) or name (string) |
Get template by client ID iterable_get_template_by_client_id | Retrieves an email template by its client-defined template ID |
Get user by ID iterable_get_user_by_id | Get a user by userId from Iterable |
Get user by ID path iterable_get_user_by_id_path | Get a user by userId (path parameter) from Iterable |
Get user events iterable_get_user_events | Get events for a specific user by userId |
Get user sent messages iterable_get_user_sent_messages | Get messages sent to a user by email address or userId |
Get web in app messages iterable_get_web_in_app_messages | Get a user's web in-app messages from Iterable |
List campaigns iterable_list_campaigns | Retrieves metadata about all campaigns in a project with optional pagination |
List catalog items iterable_list_catalog_items | Get the catalog items for a catalog |
List catalogs iterable_list_catalogs | Retrieve all catalog names from Iterable |
List channels iterable_list_channels | Get all message channels within the Iterable project |
List export files iterable_list_export_files | Get the job status and files for an export started with the 'Start export' endpoint |
List export jobs iterable_list_export_jobs | Retrieve a list of recent export jobs for the current project |
List forgotten user IDS iterable_list_forgotten_user_ids | Get hashed user IDs of forgotten users for GDPR compliance |
Try it: find the Iterable tool you need
Browse the 30 Iterable tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Iterable to export data csv and walk me through the result in plain English.
Use Iterable to export data json and walk me through the result in plain English.
Use Iterable to export user events and walk me through the result in plain English.
Pull the relevant data from Iterable, 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 Iterable working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Iterable API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Iterable 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 Iterable. | 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 Iterable actions to the runtime in a format your agent can reliably use. | 116 tools for Iterable are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Iterable 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 Iterable in the browser, and the 116 tools above work from chat. There is no SDK and no config file, and the Iterable key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Iterable skill but can't call the tools
The ClawHub skill teaches OpenClaw about Iterable, but the calls run through the ClawLink plugin and your connected account. Make sure Iterable 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 Iterable 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 Iterable tools
Iterable 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 Iterable 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.
Iterable 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 Iterable has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Iterable integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Iterable: link your Iterable account once in the browser and OpenClaw can call the Iterable API through 116 ready-made tools — no custom code or token handling.
How do I add Iterable to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Iterable skill from ClawHub, then you click Connect in the dashboard to authorize Iterable. OpenClaw calls the tools from the next message — no config files, and the Iterable key you paste is stored server-side instead of in your environment.
How long does it take to connect Iterable to OpenClaw?
About two minutes. Sign in, click Connect next to Iterable in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Iterable 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 Iterable working from chat.
OpenClaw installed the Iterable skill but can't call the tools
The ClawHub skill teaches OpenClaw about Iterable, but the calls run through the ClawLink plugin and your connected account. Make sure Iterable 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.
