Two-way sync
Changes in Insightly or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep Insightly 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.
Insightly 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 Custom Fields, Contacts, Organizations, Leads in Insightly with Commerce / Purchases, Export data, Users, Events in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — Insightly 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.
New leads or responders captured in Iterable flow into Insightly assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.
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 Insightly, so reps see interest before they reach out.
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.
| Insightly objects | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| Events Calendar items sync for a complete activity timeline. | 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}. | 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. | |
| Notes Free-text context attaches to synced records for downstream visibility. | 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. | Notes is specific to Insightly and Lists to Iterable — each maps to any object or custom field on the other side. | |
| Products Product catalog entries support line-item syncing on opportunities and quotes. | Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. | Products is specific to Insightly and Catalogs to Iterable — each maps to any object or custom field on the other side. | |
| Custom Fields Per-object custom fields carry enrichment and billing data written from external systems. | Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. | Custom Fields is specific to Insightly and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side. | |
| Contacts Person records sync with marketing and support tools to keep one contact list. | 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. | Contacts is specific to Insightly and Export data to Iterable — each maps to any object or custom field on the other side. | |
| Organizations Company records map to accounts in ERPs and other CRMs. | 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. | Organizations is specific to Insightly and Users 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.
DetectionStacksync polls Insightly for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record updated-date fields.
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 Insightly through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Insightly–Iterable connection.
Changes in Insightly or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Insightly 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 Insightly or Iterable record.
Track your Insightly ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Insightly 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 Insightly 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 Insightly 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 Insightly and Iterable: authenticate both systems, choose the objects to sync (such as Insightly's Events and Notes), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Insightly and Iterable: Where Iterable generates leads: hand-off without re-keying; New and updated people stay in step; Where Iterable captures engagement: activity lands on the record. New leads or responders captured in Iterable flow into Insightly assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.
Insightly: REST API (versioned). Authentication: API key sent via HTTP Basic authentication. 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.
Insightly: Most core objects support custom fields, which is the standard place to land externally sourced data during syncs. Iterable: Rate limits are per endpoint and return HTTP 429 when exceeded; since November 10, 2025, providing the API key in the query string or request body is throttled more strictly than the Api-Key header. Stacksync's field mapping accounts for these differences between Insightly 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 Insightly and Iterable records are not retained after a sync operation.
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 476 integrations available for Insightly and Iterable.