Skip to content
Marketing ⇄ CRM

Iterable to ZoomInfo integration — real-time data sync

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

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

ZoomInfo 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 ZoomInfo — without exports, scripts, or schedulers.

ZoomInfo 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 Align CRM account hierarchies with ZoomInfo's corporate hierarchy data.
  • 02 Enrich CRM accounts and contacts on a schedule so firmographics, titles, and phone numbers stay current.
  • 03 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.
  • 04 Push warehouse or CRM audience segments into Iterable as Users via bulkUpdate (up to 1000 per call) and subscribe them to static Lists to drive campaigns.

Common sync patterns

Segments and audiences follow the CRM

Where Iterable builds lists, segments, or ad audiences, membership tracks the fields and stage owned in ZoomInfo, so who receives a campaign reflects current pipeline reality instead of a stale export.

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

New leads or responders captured in Iterable flow into ZoomInfo 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.

What you can sync between Iterable and ZoomInfo

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 ZoomInfo 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}. Intent Signals Company-level topic scores indicating in-market buying behavior. Events is specific to Iterable and Intent Signals to ZoomInfo — 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. Scoops Event-driven signals such as leadership changes, funding rounds, and new projects. Campaigns is specific to Iterable and Scoops to ZoomInfo — 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. Technographics Technology install data per company, used for segmentation and territory planning. Templates is specific to Iterable and Technographics to ZoomInfo — 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. Company Hierarchies Parent and subsidiary linkage used to align CRM account hierarchies. Lists is specific to Iterable and Company Hierarchies to ZoomInfo — 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. Company Profiles Firmographic records covering industry, size, revenue, and location, matched against CRM accounts. Catalogs is specific to Iterable and Company Profiles to ZoomInfo — 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. Contact Profiles Person records with title, email, phone, and company linkage, used to enrich leads and contacts. Commerce / Purchases is specific to Iterable and Contact Profiles to ZoomInfo — each maps to any object or custom field on the other side.

How changes propagate between Iterable and ZoomInfo

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

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

ZoomInfo Iterable Interval-based propagation

DetectionStacksync polls ZoomInfo for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled re-enrichment and polling.

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.
  • ZoomInfo: Usage is metered by credits and contract-based limits rather than a single public rate limit.
What ships with Iterable ⇄ ZoomInfo

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Iterable ⇄ ZoomInfo 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 ZoomInfo.

How the Iterable and ZoomInfo 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.

ZoomInfo

Integration surface
REST API organized around search and enrich endpoints
Authentication
API credentials exchanged for a short-lived JWT
Change detection
Scheduled re-enrichment and polling; the platform is primarily a lookup and enrichment source, not an event stream
Capabilities
read
Rate limits
Usage is metered by credits and contract-based limits rather than a single public rate limit.
How it works

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

    Choose tables

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

Iterable and ZoomInfo 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 396 integrations available for Iterable and ZoomInfo.

Popular · 7 of 396
All Iterable integrations All ZoomInfo 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