Two-way sync
Changes in Attio or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep Attio 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.
Attio 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 Deals, Workspaces, Custom objects, People in Attio with Export data, Users, Events, Campaigns in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — Attio 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.
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.
Opens, clicks, form fills, event attendance, or ad responses recorded in Iterable post back to the contact or account in Attio, 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.
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.
| Attio objects | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| Users Synced with incremental and full sync per the Stacksync docs. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Deals Pipeline records; read out for revenue reporting and written to from automation. | 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. | Deals is specific to Attio and Export data to Iterable — each maps to any object or custom field on the other side. | |
| Workspaces Synced with incremental and full sync per the Stacksync docs. | 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}. | Workspaces is specific to Attio and Events to Iterable — each maps to any object or custom field on the other side. | |
| Custom objects Workspace-defined objects that behave like standard ones in the API. | 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. | Custom objects is specific to Attio and Campaigns to Iterable — each maps to any object or custom field on the other side. | |
| People Standard person object; synced with marketing tools and warehouse person tables. | 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. | People is specific to Attio and Templates to Iterable — each maps to any object or custom field on the other side. | |
| Companies Standard company object; matched to billing and product accounts in two-way syncs. | 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. | Companies is specific to Attio and Lists 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.
DetectionAttio notifies Stacksync of record changes through webhook events. Webhooks on record and list-entry events, with polling as a fallback.
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 Attio through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Attio–Iterable connection.
Changes in Attio or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Attio 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 Attio or Iterable record.
Track your Attio ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Attio 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 Attio 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 Attio 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 Attio and Iterable: authenticate both systems, choose the objects to sync (such as Attio's Users and Deals), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Attio and Iterable: New and updated people stay in step; Where Iterable captures engagement: activity lands on the record; Lead and lifecycle status agree. 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.
Attio: REST API. Authentication: Guided in-app connection ("Attio CRM" connection created in a few clicks, "without any coding required"); the docs do not name the underlying auth mechanism (OAuth vs API key). 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.
Attio: Docs do not document the authentication mechanism, change-detection method, or write/CDC/webhook behavior for Attio. Iterable: Bulk endpoints cap at 1000 records per call - /api/users/bulkUpdate accepts up to 1000 users and /api/events/trackBulk up to 1000 events. Stacksync's field mapping accounts for these differences between Attio 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 Attio and Iterable records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Attio and Iterable connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Attio–Iterable integration in-house.
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 490 integrations available for Attio and Iterable.