Two-way sync
Changes in Airtable or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep Airtable 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.
Iterable holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in Airtable, hard to get into campaigns without manual exports.
Stacksync mirrors Export data, Users, Events, Campaigns from Iterable into Attachments, Collaborators, Bases, Tables in Airtable field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in Airtable, from usage, orders, or account status, sync back into Iterable to drive campaigns and ads, with Iterable kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.
A new lead, form fill, or list change in Iterable arrives as a row change in Airtable, so scoring, jobs, and notifications run in the tooling your team already uses.
Lifecycle stage, subscription status, or plan maintained on either side stays current on the other, ending exports and dual data entry.
Contacts, leads, audiences, and campaign metrics from Iterable live in Airtable as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.
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.
| Airtable objects | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| Tables Map to sync tables; schema is readable through the base metadata endpoints. | 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. | Tables is specific to Airtable and Lists to Iterable — each maps to any object or custom field on the other side. | |
| Records The row-level unit created, updated, and deleted during syncs, identified by rec-prefixed IDs. | Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. | Records is specific to Airtable and Catalogs to Iterable — each maps to any object or custom field on the other side. | |
| Fields Typed columns including linked records, lookups, and rollups; computed fields are read-only in syncs. | Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. | Fields is specific to Airtable and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side. | |
| Views Filtered subsets of a table that can scope which records a sync reads. | 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. | Views is specific to Airtable and Export data to Iterable — each maps to any object or custom field on the other side. | |
| Linked records Cross-table references that carry relationships between synced tables. | 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. | Linked records is specific to Airtable and Users to Iterable — each maps to any object or custom field on the other side. | |
| Attachments File fields exposed as expiring URLs that syncs can mirror to other systems. | 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}. | Attachments is specific to Airtable and Events 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.
DetectionAirtable pushes changes as they happen — webhook events backed by change data capture. Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks).
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 Airtable through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Airtable–Iterable connection.
Changes in Airtable or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Airtable 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 Airtable or Iterable record.
Track your Airtable ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Airtable 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 Airtable 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 Airtable 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 Airtable and Iterable: authenticate both systems, choose the objects to sync (such as Airtable's Tables and Records), map fields visually, and changes propagate both ways in milliseconds — no code required.
Airtable: Every base exposes its own REST endpoint, and the metadata API lets integrations read table and field schemas programmatically. Iterable: Iterable authenticates with an API key in the Api-Key header (also accepted as Api_Key; the name is case-insensitive); keys are scoped by type - Server-side, JavaScript/Web, or Mobile. Stacksync's field mapping accounts for these differences between Airtable and Iterable without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Airtable and Iterable records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Airtable and Iterable connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Airtable–Iterable integration in-house.
Yes — Stacksync ships production-grade connectors for both Airtable and Iterable. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Airtable: Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks); formula fields don't emit change events and are re-synced every hour. 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.
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 501 integrations available for Airtable and Iterable.