Skip to content
Marketing ⇄ Accounting and finance

Iterable to Navan integration — real-time, two-way sync

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

Put revenue reality behind every campaign: Navan and Iterable share the same customers, contacts, and billing status in real time, in both directions.

Navan records the money — who pays, how much, and whether they are current; Iterable decides who hears from the business and what they hear. The two overlap wherever the same customers and contacts matter to both, and when that overlap is bridged by CSV exports or an overnight batch, campaigns target on stale billing data and finance works from lists marketing has already changed underneath it.

Stacksync syncs Repayments, Fees, and Adjustments, Users, Card Transactions, Connect Transactions in Navan with Events, Campaigns, Templates, Lists in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — finance keeps the revenue and payment truth, marketing keeps consent and engagement — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Users and department mappings from an HRIS into reporting tables so every transaction is attributed to a cost center and manager.
  • 02 Sync Card Transactions and Manual Transactions into Postgres or a warehouse so finance analyzes corporate spend in SQL without manual CSV exports.
  • 03 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.
  • 04 Track product and revenue Events (custom events, trackPurchase, updateCart) into Iterable from an app or database so journeys trigger on live behavior.

Common sync patterns

Where Navan tracks lifecycle state: keep Iterable current

Trial, renewal, churn, or payment state from Navan updates the contact in Iterable, so lifecycle campaigns and audience suppression run on current billing reality.

Consent and contact details stay aligned

Email, phone, address, and opt-out flags kept in either system stay consistent in the other, so every send and record honors the latest preferences.

Revenue and billing signals reach the audience

Plan tier, spend, or payment status from Navan lands on the matching record in Iterable, so segments and targeting reflect who actually pays and how much.

What you can sync between Iterable and Navan

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 Navan objects How this pairing syncs
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. Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. 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.
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. Receipts Receipt images tied to each transaction; fetched read-only through presigned URLs for archival in a warehouse or document store. Lists is specific to Iterable and Receipts to Navan — 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. Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. Catalogs is specific to Iterable and Repayments, Fees, and Adjustments to Navan — 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. Card Transactions Navan physical and virtual card spend; read via GET, then GL codes, cost centers, and ERP sync status are written back per transaction through the transaction update endpoint. Commerce / Purchases is specific to Iterable and Card Transactions to Navan — each maps to any object or custom field on the other side.
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. Connect Transactions External and personal card feed matched into Navan; retrieved read-only and coded with custom-field values through the transaction update endpoint. Export data is specific to Iterable and Connect Transactions to Navan — each maps to any object or custom field on the other side.
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}. Manual Transactions Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan. Events is specific to Iterable and Manual Transactions to Navan — each maps to any object or custom field on the other side.

How changes propagate between Iterable and Navan

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

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

Navan Iterable Sub-second propagation

DetectionNavan notifies Stacksync of record changes through webhook events. Navan's Expense API supports webhooks for transaction and expense events.

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.
  • Navan: Requests are throttled with HTTP 429 and Navan recommends retrying with exponential backoff; the Expense/Public API must first be enabled per account by Navan.
What ships with Iterable ⇄ Navan

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Navan

Integration surface
REST (Expense API and Booking API)
Authentication
OAuth 2.0 client-credentials flow; an admin creates a client_id and client_secret under Settings > Integrations and exchanges them at Navan's OAuth token endpoint for a short-lived bearer token that is refreshed on expiry (separate US and EU regional hosts)
Change detection
Navan's Expense API supports webhooks for transaction and expense events; sync engines also poll GET endpoints with date-range and updatedAt filters (createdFrom/createdTo for bookings) to backfill history and reconcile. There is no database-level CDC.
Capabilities
read · write · webhooks
Rate limits
Requests are throttled with HTTP 429 and Navan recommends retrying with exponential backoff; the Expense/Public API must first be enabled per account by Navan.
How it works

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

    Choose tables

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

Iterable and Navan 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 461 integrations available for Iterable and Navan.

Popular · 8 of 461
All Iterable integrations All Navan 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