Skip to content
CRM ⇄ Marketing

Creatio CRM to Iterable integration — real-time, two-way sync

Keep Creatio CRM and Iterable in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Creatio CRM and Iterable

Keep the people you sell to and the people you market to in one shared view: Creatio CRM and Iterable sync contacts, accounts, and engagement in real time, in both directions.

Creatio CRM owns the customer relationship and the pipeline; Iterable runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.

Stacksync syncs Products, Custom sections (objects), Accounts, Contacts in Creatio CRM with Campaigns, Templates, Lists, Catalogs in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — Creatio CRM can own account and opportunity status while Iterable owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Creatio accounts and opportunities into a warehouse for pipeline and forecast reporting outside Creatio dashboards.
  • 02 Two-way sync of accounts, orders, and products between Creatio and an ERP so sales and fulfillment share one record of truth.
  • 03 Stream Iterable System Webhook events into a database in near real time so opens, clicks, bounces, and unsubscribes land alongside CRM contact records.
  • 04 Write list subscribe/unsubscribe changes from a CRM back into Iterable Lists so suppression and opt-in state stay current before the next send.

Common sync patterns

Where Iterable generates leads: hand-off without re-keying

New leads or responders captured in Iterable flow into Creatio CRM assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.

New and updated people stay in step

When a contact or lead is created or edited in either system, the matching record appears or updates in the other, so campaigns reach real people and reps see who is already being marketed to.

Where Iterable captures engagement: activity lands on the record

Opens, clicks, form fills, event attendance, or ad responses recorded in Iterable post back to the contact or account in Creatio CRM, so reps see interest before they reach out.

What you can sync between Creatio CRM and Iterable

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Creatio CRM objects Iterable objects How this pairing syncs
Accounts Company records at the center of Creatio's CRM model; commonly synced with ERP customer masters. Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. Accounts is specific to Creatio CRM and Users to Iterable — each maps to any object or custom field on the other side.
Contacts Person records linked to accounts, activities, and cases. Events Custom and system events tracked via /api/events/track and /api/events/trackBulk (up to 1000 events per call); a single user's event history is read via GET /api/events/{email}. Contacts is specific to Creatio CRM and Events to Iterable — each maps to any object or custom field on the other side.
Leads Inbound interest records qualified into opportunities; synced for funnel reporting. Campaigns Email, SMS, push, and in-app sends; metadata and metrics read via GET /api/campaigns and /api/campaigns/metrics, created and sent via /api/campaigns/create and /api/campaigns/trigger. Leads is specific to Creatio CRM and Campaigns to Iterable — each maps to any object or custom field on the other side.
Opportunities Deal records with stages and amounts used in revenue syncs. Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. Opportunities is specific to Creatio CRM and Templates to Iterable — each maps to any object or custom field on the other side.
Activities Tasks, calls, and meetings tied to records for engagement tracking. Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. Activities is specific to Creatio CRM and Lists to Iterable — each maps to any object or custom field on the other side.
Cases Service requests handled in Creatio's service workflows; syncable to help desk tools. Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Cases is specific to Creatio CRM and Catalogs to Iterable — each maps to any object or custom field on the other side.

How changes propagate between Creatio CRM and Iterable

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Creatio CRM Iterable Interval-based propagation

DetectionStacksync polls Creatio CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on ModifiedOn system columns.

DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.

Iterable Creatio CRM Sub-second propagation

DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.

DeliveryEach detected change is written to Creatio CRM through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Creatio CRM: Subject to the platform's API rate limits.
  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
What ships with Creatio CRM ⇄ Iterable

Connect Creatio CRM and Iterable for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Creatio CRM–Iterable connection.

Real-time

Two-way sync

Changes in Creatio CRM or Iterable instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Creatio CRM or Iterable data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Creatio CRM or Iterable record.

Observability

Monitoring

Track your Creatio CRM ⇄ Iterable sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Creatio CRM and Iterable.

How the Creatio CRM and Iterable connectors work

Creatio CRM

Integration surface
OData REST API plus a proprietary DataService API
Authentication
OAuth 2.0 or cookie-based session authentication
Change detection
Polling on ModifiedOn system columns; outbound notifications require configuring business processes
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits

Iterable

Integration surface
Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication
API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com.
Change detection
System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
How it works

How to connect Creatio CRM to Iterable — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Creatio CRM and Iterable with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Creatio CRM connected
    Iterable connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Creatio CRM and Iterable objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Creatio CRM ⇄ Iterable
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Creatio CRM Iterable
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Creatio CRM and Iterable integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 384 integrations available for Creatio CRM and Iterable.

Popular · 8 of 384
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.