Two-way sync
Changes in Infor CRM or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep Infor 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.
Infor 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 Custom entities, Accounts, Contacts, Leads in Infor CRM with Users, Events, Campaigns, Templates in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — Infor 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.
Opens, clicks, form fills, event attendance, or ad responses recorded in Iterable post back to the contact or account in Infor CRM, so reps see interest before they reach out.
Status, stage, or score set in one system updates the matching record in the other, so a lead marketing is still nurturing is not worked as sales-ready, and a closed account stops receiving prospecting.
Where Iterable builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Infor CRM, so who receives a campaign reflects current pipeline reality instead of a stale export.
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.
| Infor CRM objects | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| Campaigns Marketing containers linked to leads and opportunities. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Accounts Company records matched against ERP customer masters in syncs. | 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 Infor CRM and Users to Iterable — each maps to any object or custom field on the other side. | |
| Contacts Person records synced with marketing and support tools. | 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 Infor CRM and Events to Iterable — each maps to any object or custom field on the other side. | |
| Leads Unqualified records synced in from marketing sources. | 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. | Leads is specific to Infor CRM and Templates to Iterable — each maps to any object or custom field on the other side. | |
| Opportunities Pipeline records synced out for forecasting and reporting. | 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. | Opportunities is specific to Infor CRM and Lists to Iterable — each maps to any object or custom field on the other side. | |
| Tickets Service records synced with helpdesk and field service systems. | Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. | Tickets is specific to Infor 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 Infor CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on modified timestamps.
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 Infor CRM through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Infor CRM–Iterable connection.
Changes in Infor CRM or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Infor 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 Infor CRM or Iterable record.
Track your Infor CRM ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Infor 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 Infor 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 Infor 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 Infor CRM and Iterable: authenticate both systems, choose the objects to sync (such as Infor CRM's Campaigns and Accounts), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Infor CRM: Polling on modified timestamps; no log-based CDC on the API surface. 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 Infor CRM side: Custom entities, Accounts, Contacts, Leads, plus custom fields where Infor CRM exposes them. On the Iterable side: Users, Events, Campaigns, Templates. 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.
Common patterns for Infor CRM and Iterable: Where Iterable captures engagement: activity lands on the record; Lead and lifecycle status agree; Segments and audiences follow the CRM. Opens, clicks, form fills, event attendance, or ad responses recorded in Iterable post back to the contact or account in Infor CRM, so reps see interest before they reach out.
Infor CRM: REST-style SData API over the CRM entity model. Authentication: User credentials; Infor OS-managed authentication in cloud deployments. Iterable: 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. Stacksync manages authentication, retries, and rate limits on both sides.
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 482 integrations available for Infor CRM and Iterable.