Iterable

Iterable

This connector reads and writes Iterable (cross-channel marketing) through the Iterable API with a server-side API key: lists, users and their events and sent messages, campaigns and their metrics, templates, channels, message types and catalogs; it can also update profiles, track events, change list membership and send a triggered email to one user.

Setup (about 3 minutes)

1. In Iterable open Integrations, API Keys (project settings) and click New API Key. Choose a Server-side key for reads and writes, or a Read-only key if the connector should only read. JavaScript and Mobile keys do not work here.
2. Copy the key and paste it into ITERABLE_API_KEY. Keys belong to one project.
3. Set ITERABLE_API_URL to the project's data center: https://api.iterable.com for US projects, https://api.eu.iterable.com for EU projects (app.eu.iterable.com).

The key acts for the whole project, not for one person: whoever uses this connector sees every user and campaign the key can read. Share the MCP server only with people allowed to see that.

Limits (per project): most reads 100 calls a second; campaign metrics 10 a minute; list users and list size 5 a minute; sent messages 3 a second. Iterable answers 429 when a limit is reached.

How to work

1. People: iterable_get_user_by_email or iterable_get_user_by_id for the profile, iterable_get_user_events_by_email or iterable_get_user_events_by_user_id for what they did and received, iterable_get_sent_messages for the messages sent to them.
2. Lists: iterable_list_lists, iterable_get_list_size and iterable_list_list_users (plain text, one user per line, cut at about 100 KB).
3. Campaigns: iterable_list_campaigns (page by page, filter by state), iterable_get_campaign, then iterable_get_campaign_metrics for one or more campaign ids. The metrics come back as CSV text: the first line holds the column names, each further line one campaign.
4. Content and setup: iterable_list_templates, iterable_list_channels, iterable_list_message_types, iterable_list_catalogs and iterable_list_catalog_items.
5. Writes, each only after the user confirms: iterable_update_user merges profile fields, iterable_track_event records an event, iterable_subscribe_to_list and iterable_unsubscribe_from_list change list membership (they can start journeys or stop messages). iterable_send_email sends a real email from a triggered campaign to one person: show the campaign, the recipient and the data first.
6. iterable_delete_user_by_email and iterable_delete_user_by_user_id delete profiles for good and are installed switched off; an administrator turns them on deliberately.

Identify a user by email or by user_id, not both, depending on whether the project is email-based, userID-based or hybrid. Iterable times are epoch milliseconds in answers; filters take the formats named in each parameter.

Common errors

• 401 "Invalid API key": the key is wrong, deleted, of the wrong type (JavaScript or Mobile), or from the other data center; check ITERABLE_API_URL.
• 400 with a code such as BadParams or RequestFieldsTypesMismatched: a parameter or a field type is wrong; msg says which.
• 404 / NotFound: the user, list or campaign does not exist in this project.
• 429: the rate limit is reached; wait and retry once.

Out of scope here: export jobs, bulk endpoints, template and snippet editing, experiments, journeys (workflows), in-app, push, SMS and web push sends, subscriptions per message type, and catalog changes.