Skip to content
Accounting and finance ⇄ Marketing

Navan to Salesforce Marketing Cloud integration — real-time, two-way sync

Keep Navan and Salesforce Marketing Cloud 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 Navan and Salesforce Marketing Cloud

Put revenue reality behind every campaign: Navan and Salesforce Marketing Cloud 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; Salesforce Marketing Cloud 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 Card Transactions, Connect Transactions, Manual Transactions, Bookings in Navan with Content Assets (Content Builder), Automations (Automation Studio), Tracking Events, Transactional Sends in Salesforce Marketing Cloud 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 Card Transactions and Manual Transactions into Postgres or a warehouse so finance analyzes corporate spend in SQL without manual CSV exports.
  • 02 Push coded expense transactions into an accounting system, then set their ERP sync status in Navan so the same records are not exported twice.
  • 03 Sync Contacts and Subscriber Key subscription status between Marketing Cloud and a CRM so suppression and opt-in state stay current before the next send.
  • 04 Stream Event Notification Service callbacks for transactional sends, bounces, opens, and clicks into a database in near real time alongside CRM contact records.

Common sync patterns

Revenue and billing signals reach the audience

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

One customer and contact list

Where both systems keep customer or contact records, an edit on either side propagates to the other, ending dual maintenance and the drift it creates.

Where Salesforce Marketing Cloud captures new people: clean records flow to finance

Registrants, form fills, or leads created in Salesforce Marketing Cloud create or update the matching customer or contact in Navan, so billing and reporting start from accurate details without re-entry.

What you can sync between Navan and Salesforce Marketing Cloud

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.

Navan objects Salesforce Marketing Cloud objects How this pairing syncs
Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. Content Assets (Content Builder) Emails, templates, images, and reusable content blocks stored in Content Builder and read or written via /asset/v1/content/assets, used to compose the messages a journey or send delivers. Repayments, Fees, and Adjustments is specific to Navan and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. Automations (Automation Studio) Scheduled or triggered workflows of import, query, extract, and send activities managed via /automation/v1/automations; SQL Query Activities read Data Views and write results into Data Extensions. Users is specific to Navan and Automations (Automation Studio) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
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. Tracking Events Sent, Open, Click, Bounce, Unsubscribe, and NotSent events retrieved through the SOAP tracking objects (SentEvent, OpenEvent, ClickEvent, BounceEvent) or the Automation Studio Data Views (_Sent, _Open, _Click, _Bounce) - the queryable record of engagement per send. Card Transactions is specific to Navan and Tracking Events to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Connect Transactions External and personal card feed matched into Navan; retrieved read-only and coded with custom-field values through the transaction update endpoint. Transactional Sends Triggered and transactional Email/SMS delivered through the Messaging API (/messaging/v1/email/messages/{key}); the Event Notification Service reports each message's disposition (delivered, bounced, opened, clicked). Connect Transactions is specific to Navan and Transactional Sends to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Manual Transactions Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan. Data Extensions Custom relational tables that store subscriber, audience, and arbitrary business data; rows are read via GET /data/v1/customobjectdata or SOAP Retrieve and upserted via the synchronous rowset PUT or the async /data/v1/async/dataextensions rows endpoint. This is the primary two-way surface. Manual Transactions is specific to Navan and Data Extensions to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Bookings Flight, hotel, rail, and car reservations from the Booking API; pulled read-only by createdFrom/createdTo date range for trip and travel-spend reporting. Contacts / Subscribers The contact model keyed by Subscriber Key, holding channel addresses and subscription status; managed through the Contacts API (/contacts/v1/contacts) and the SOAP Subscriber object, and referenced by every send and journey. Bookings is specific to Navan and Contacts / Subscribers to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.

How changes propagate between Navan and Salesforce Marketing Cloud

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.

Navan Salesforce Marketing Cloud 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 Salesforce Marketing Cloud through its API, with automatic retries and rate-limit backoff.

Salesforce Marketing Cloud Navan Sub-second propagation

DetectionSalesforce Marketing Cloud notifies Stacksync of record changes through webhook events. The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback.

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

Rate-limit considerations

  • 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.
  • Salesforce Marketing Cloud: Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
What ships with Navan ⇄ Salesforce Marketing Cloud

Connect Navan and Salesforce Marketing Cloud for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Navan ⇄ Salesforce Marketing Cloud sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Navan and Salesforce Marketing Cloud.

How the Navan and Salesforce Marketing Cloud connectors work

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.

Salesforce Marketing Cloud

Integration surface
Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
Authentication
OAuth 2.0 via an Installed Package (Client ID + Client Secret). Server-to-server uses the client_credentials grant and web apps use authorization_code, both against {subdomain}.auth.marketingcloudapis.com/v2/token. The 20-minute access token response also returns the account's rest_instance_url and soap_instance_url.
Change detection
The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback URL and subscription are registered and verified. There is no general data-change feed, so Data Extension and Data View syncs poll by date fields.
Capabilities
read · write · webhooks
Rate limits
Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
How it works

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

    Choose tables

    Pick the Navan and Salesforce Marketing Cloud 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 · Navan ⇄ Salesforce Marketing Cloud
    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
    Navan Salesforce Marketing Cloud
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Navan and Salesforce Marketing Cloud 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 461 integrations available for Navan and Salesforce Marketing Cloud.

Popular · 8 of 461
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.