Skip to content
Marketing ⇄ ERP

Iterable to Rootstock ERP integration — real-time, two-way sync

Keep Iterable and Rootstock ERP 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 Iterable and Rootstock ERP

Feed the real customer, order, and revenue records from Rootstock ERP into Iterable so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.

Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. Rootstock ERP holds exactly that: Receipts and Shipments, Salesforce Accounts and Contacts, Sales Orders, Work Orders that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.

Stacksync syncs Receipts and Shipments, Salesforce Accounts and Contacts, Sales Orders, Work Orders in Rootstock ERP with Commerce / Purchases, Export data, Users, Events in Iterable in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Iterable works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Iterable flow back onto the record in Rootstock ERP.

The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.

Common use cases

  • 01 Push confirmed sales orders to a 3PL or WMS and write shipment confirmations back to Rootstock.
  • 02 Replicate work order and inventory data to a Postgres database or warehouse for shop-floor and planning analytics.
  • 03 Write list subscribe/unsubscribe changes from a CRM back into Iterable Lists so suppression and opt-in state stay current before the next send.
  • 04 Two-way sync User profiles and their custom data fields between Iterable and a Postgres database or CRM so attributes and subscription state stay aligned in both systems.

Common sync patterns

Suppress or target existing customers

Because Rootstock ERP knows who is already a paying customer, Iterable can exclude them from acquisition campaigns or single them out for renewal and cross-sell.

One customer identity across both systems

A person or company's contact details corrected in either system update the other, so marketing and the back office stop maintaining separate versions of the same record.

Lifecycle triggers from back-office events

A first order, a renewal, or a lapsed account recorded in Rootstock ERP appears in Iterable within seconds, ready to start or stop a lifecycle campaign.

What you can sync between Iterable and Rootstock ERP

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.

Iterable objects Rootstock ERP objects How this pairing syncs
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}. Bills of Material Multi-level product structures read for costing and planning integrations. Events is specific to Iterable and Bills of Material to Rootstock ERP — each maps to any object or custom field on the other side.
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. Inventory Balances On-hand quantities by site and location, synced to storefronts and WMS. Campaigns is specific to Iterable and Inventory Balances to Rootstock ERP — each maps to any object or custom field on the other side.
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. Receipts and Shipments Inbound and outbound transactions synced to logistics and 3PL systems. Templates is specific to Iterable and Receipts and Shipments to Rootstock ERP — each maps to any object or custom field on the other side.
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. Salesforce Accounts and Contacts Shared CRM masters in the same org, so customer data needs no separate ERP sync. Lists is specific to Iterable and Salesforce Accounts and Contacts to Rootstock ERP — each maps to any object or custom field on the other side.
Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Sales Orders Order headers and lines synced to fulfillment, invoicing, and reporting systems. Catalogs is specific to Iterable and Sales Orders to Rootstock ERP — each maps to any object or custom field on the other side.
Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. Work Orders Manufacturing execution records synced to MES, scheduling, and analytics tools. Commerce / Purchases is specific to Iterable and Work Orders to Rootstock ERP — each maps to any object or custom field on the other side.

How changes propagate between Iterable and Rootstock ERP

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.

Iterable Rootstock ERP 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 Rootstock ERP through its API, with automatic retries and rate-limit backoff.

Rootstock ERP Iterable Sub-second propagation

DetectionChanges in Rootstock ERP are captured at the source via change data capture — no polling loop against its API. Salesforce Change Data Capture on Rootstock custom objects where enabled (entity selection limits apply).

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

Rate-limit considerations

  • 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.
  • Rootstock ERP: Consumes the Salesforce org's daily API request allocation, shared with other integrations.
What ships with Iterable ⇄ Rootstock ERP

Connect Iterable and Rootstock ERP for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Iterable or Rootstock ERP 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 Iterable or Rootstock ERP record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Iterable and Rootstock ERP.

How the Iterable and Rootstock ERP connectors work

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.

Rootstock ERP

Integration surface
Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects
Authentication
OAuth 2.0 (standard Salesforce connected app flows)
Change detection
Salesforce Change Data Capture on Rootstock custom objects where enabled (entity selection limits apply); SOQL polling on SystemModstamp as fallback
Capabilities
read · write · CDC
Rate limits
Consumes the Salesforce org's daily API request allocation, shared with other integrations
How it works

How to connect Iterable to Rootstock ERP — 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 Iterable and Rootstock ERP 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
    Iterable connected
    Rootstock ERP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Iterable and Rootstock ERP 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 · Iterable ⇄ Rootstock ERP
    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
    Iterable Rootstock ERP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Iterable and Rootstock ERP 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 368 integrations available for Iterable and Rootstock ERP.

Popular · 4 of 368
All Iterable integrations All Rootstock ERP integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own