Skip to content
CRM ⇄ Marketing

Crustdata to Iterable integration — real-time data sync

Keep Crustdata 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 Crustdata and Iterable

Flow Crustdata data into Iterable in real time — no exports, no schedulers, no custom scripts.

Crustdata is a read-only source: Stacksync reads its data in real time and delivers it into Iterable, so Iterable always reflects the current state of Crustdata — without exports, scripts, or schedulers.

Crustdata 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.

Common use cases

  • 01 Stream screener results into a warehouse to maintain a living TAM and target-account universe.
  • 02 Append enrichment at lead-capture time so new records arrive scored and routable.
  • 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

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

New leads or responders captured in Iterable flow into Crustdata 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 Crustdata, so reps see interest before they reach out.

What you can sync between Crustdata 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.

Crustdata objects Iterable objects How this pairing syncs
Enrichment Responses Real-time enrichment lookups keyed by domain or profile URL; read to append fresh firmographic and contact data at form-fill or record-creation time. 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. Enrichment Responses is specific to Crustdata and Lists to Iterable — each maps to any object or custom field on the other side.
Companies Firmographic records — industry, size, funding, growth signals; read out to enrich CRM accounts and warehouse company tables. Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Companies is specific to Crustdata and Catalogs to Iterable — each maps to any object or custom field on the other side.
People Contact and profile data for decision-makers; read into a CRM or outreach tool to fill missing titles, emails, and LinkedIn profiles. Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. People is specific to Crustdata and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side.
Headcount and Growth Metrics Time-series employee counts by department and region; read to score accounts on hiring momentum and expansion signals. Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. Headcount and Growth Metrics is specific to Crustdata and Export data to Iterable — each maps to any object or custom field on the other side.
Tech Stack Detected technologies per company; read to build segments and route accounts by the tools they already use. 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. Tech Stack is specific to Crustdata and Users to Iterable — each maps to any object or custom field on the other side.
Screener Results Saved company searches with filter criteria; read on a schedule so target-account lists in the CRM refresh as companies enter the criteria. 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}. Screener Results is specific to Crustdata and Events to Iterable — each maps to any object or custom field on the other side.

How changes propagate between Crustdata 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.

Crustdata Iterable Interval-based propagation

DetectionStacksync polls Crustdata for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: real-time enrichment endpoints for on-demand lookups plus periodic re-pulls of screeners and datasets.

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

Iterable Crustdata 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.

DeliveryCrustdata does not accept inbound record writes, so this direction carries requests rather than records: Crustdata's output flows back as field updates on the originating Iterable records.

Rate-limit considerations

  • Crustdata: Requests are metered by plan credits and per-minute rate limits; bulk dataset pulls are the efficient path for large refreshes rather than per-record enrichment calls.
  • 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 Crustdata ⇄ Iterable

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Crustdata and Iterable connectors work

Crustdata

Integration surface
REST API (JSON)
Authentication
API token — Authorization: Token header issued per workspace
Change detection
Pull-based: real-time enrichment endpoints for on-demand lookups plus periodic re-pulls of screeners and datasets; no webhooks or change feed
Capabilities
read
Rate limits
Requests are metered by plan credits and per-minute rate limits; bulk dataset pulls are the efficient path for large refreshes rather than per-record enrichment calls.

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 Crustdata 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 Crustdata 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
    Crustdata connected
    Iterable connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Crustdata 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.

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 264 integrations available for Crustdata and Iterable.

Popular · 6 of 264
All Crustdata integrations All Iterable 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