Two-way sync
Changes in Creatio CRM or Iterable instantly reflect in both systems. No stale data, no manual imports.
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.
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.
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.
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.
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.
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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Creatio CRM–Iterable connection.
Changes in Creatio CRM or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Creatio CRM or Iterable data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Creatio CRM or Iterable record.
Track your Creatio CRM ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Creatio CRM and Iterable.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Creatio CRM and Iterable: authenticate both systems, choose the objects to sync (such as Creatio CRM's Accounts and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Creatio CRM and Iterable connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Creatio CRM–Iterable integration in-house.
Yes — Stacksync ships production-grade connectors for both Creatio CRM and Iterable. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Creatio CRM: Polling on ModifiedOn system columns; outbound notifications require configuring business processes. On Iterable: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Creatio CRM side: Products, Custom sections (objects), Accounts, Contacts, plus custom fields where Creatio CRM exposes them. On the Iterable side: Campaigns, Templates, Lists, Catalogs. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 384 integrations available for Creatio CRM and Iterable.