Faster time to integration
Ship in-app Iterable automations without building each API integration.
Iterable Connector
Embed Iterable inside your SaaS to sync user profiles, push event data, trigger campaigns and manage templates and journeys so customers run personalized cross-channel marketing without leaving your product.
Governed MCP tools
Expose curated Iterable methods as controlled, auditable tools.
Reusable orchestration
Create once and reuse journeys, triggers and mappings across tenants.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
What you can integrate and automate with Iterable
Teams can sync user records, send event tracking, manage lists, templates and trigger campaigns or journeys using Iterable’s REST API. Cyclr’s connector maps to Iterable endpoints for users, events, campaigns, lists, templates, webhooks and journeys, enabling in-app orchestration and customer-facing automations. (support.iterable.com)
PRODUCT USE CASES
Top Use Cases for Iterable Integrations
Quickly create integrations that sync your app’s users to Iterable, track events to trigger campaigns, manage templates and run exported reports — then publish these integrations via Cyclr’s embedded marketplace for customers to self-install. (support.iterable.com)
Sync user profiles to Iterable
Create or update users in Iterable via POST /api/users/update to keep marketing profiles synchronized with your application. (support.iterable.com)
Trigger campaigns from user events
Send events with POST /api/events/track to trigger Journeys or campaign logic based on customer activity. (support.iterable.com)
Manage and trigger campaigns
List, create and trigger campaigns using GET /api/campaigns and POST /api/campaigns/trigger endpoints. (support.iterable.com)
ORCHESTRATION
How Iterable works with Cyclr
Cyclr sits between your SaaS product and Iterable to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Iterable
Iterable processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Iterable methods you can orchestrate through Cyclr.
Users2
Get User by ID
ActionGet a user by their ID.
Get User by Email
ActionGet a user by their email address.
Lists3
Get List Users
ActionGet all users within a list.
Get New Lists
ActionGet all lists within a project created since the last successful run date.
Get Lists
ActionGet all lists within a project.
Campaigns5
List New Campaigns
ActionGet metadata about campaigns created since last successful run.
List Campaigns
ActionGet metadata about campaigns in a project.
List Child Campaigns
ActionGet metadata about child campaigns in a recurring campaign.
List Updated Campaigns
ActionGet metadata about campaigns updated since last successful run.
List Campaign Metrics
ActionList metrics for a campaign.
Journeys1
Trigger Journey
ActionTriggers a journey (formally known as a workflow).
TECHNICAL DETAILS
Iterable integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Iterable integrations in Cyclr.
API and authentication
- API host
https://api.iterable.com- Authentication
- API key
- Credentials
Customer Iterable API key (Api-Key); optional JWT Authorization header for JWT-enabled keys.
- Method categories
Users; Events; Campaigns; Lists; Templates; Journeys; Webhooks; Exports.
Pagination and rate limits
Pagination
List endpoints return arrays; per-endpoint pagination details vary — check Iterable’s endpoint docs for limit/offset or other pagination fields. (support.iterable.com)
Rate limits
Iterable applies rate limits; 429 RateLimitExceeded responses indicate throttling. Confirm per-endpoint or project limits in Iterable docs. (support.iterable.com)
IMPLEMENTATION
Authentication at a glance
Cyclr requires the customer’s Iterable API key during connector installation; Iterable authenticates requests with an Api-Key header. JWT-enabled keys may also require an Authorization Bearer header. (community.cyclr.com)
- Authentication method
- API key
- Credential required
Customer Iterable API key (Api-Key); optional JWT Authorization header for JWT-enabled keys.
Before you begin:
View setup guideAPI keys are data-center specific — use the matching API host for the customer’s project. (support.iterable.com)
COMMON QUESTIONS
Frequently asked questions
It syncs user records, posts tracked events, manages lists and templates, and triggers campaigns or journeys through Iterable’s REST API. These map to Iterable endpoints such as /api/users, /api/events and /api/campaigns. (support.iterable.com)
You provide the customer’s Iterable API key during connector installation; Cyclr sends it as the Api-Key header. JWT-enabled keys can require an Authorization Bearer header for user-scoped calls. (community.cyclr.com)
Yes. Cyclr supports multi-tenant, white-label delivery so you can install per-customer Iterable API keys and orchestrations for each account. Connector installs use each customer’s API key. (community.cyclr.com)
Yes. Cyclr lets you expose curated Iterable actions (for example, create user, track event, trigger campaign) as governed MCP tools with role and usage controls. Governance is applied in Cyclr Console. (community.cyclr.com)
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorAkeneo
Related Marketing connector for customer-facing integration workflows.
Related connectorAmazon Selling Partner
Related Marketing connector for customer-facing integration workflows.
Related connectorBluecore
Related Marketing connector for customer-facing integration workflows.