Skip to content
Accounting and finance

Connect Navan to any app with two-way sync.

Two-way sync Navan across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Navan.

These objects sync between Navan and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Navan exposes them.

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.
Connect Transactions
External and personal card feed matched into Navan; retrieved read-only and coded with custom-field values through the transaction update endpoint.
Manual Transactions
Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan.
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.
Custom Fields
Company metadata such as cost centers and project codes; discovered via GET and their option lists created or updated via async POST.
Receipts
Receipt images tied to each transaction; fetched read-only through presigned URLs for archival in a warehouse or document store.
Repayments, Fees, and Adjustments
Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers.
Users
Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments.
API surface

How Stacksync connects to Navan.

The connector runs on Navan's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

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

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
What ships with Navan

Connect Navan for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Navan instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Navan connector.

Navan (formerly TripActions) is the corporate travel, expense, and card platform where a company's T&E spend lives. It is owned by finance operations and accounting, while travel program managers set policy. Card Transactions, Manual Transactions, Bookings, and Custom Fields such as cost centers make it the system of engagement for employee spend and the record of what was booked and charged before data reaches the ERP. Users are usually provisioned from an HRIS.

  • Finance operations
  • Accounting and AP teams
  • FP&A
  • Data engineering
  • Travel program managers

  1. Sync Card Transactions and Manual Transactions into Postgres or a warehouse so finance analyzes corporate spend in SQL without manual CSV exports.

  2. Write GL codes, cost centers, and custom-field values from an ERP such as NetSuite back onto Navan transactions through the Expense API's transaction update endpoints.

  3. Push coded expense transactions into an accounting system, then set their ERP sync status in Navan so the same records are not exported twice.

  4. Pull Bookings by date range into a database to reconcile travel reservations against Card Transactions and monitor travel-policy spend.

  5. Sync Users and department mappings from an HRIS into reporting tables so every transaction is attributed to a cost center and manager.

  6. Two-way: pull Card and Manual Transactions into Postgres for spend analytics, then write GL codes and cost-center values computed against your chart of accounts back onto each transaction via Navan's transaction update endpoints.

All Navan integrations

Pick the system you need to keep in sync with Navan. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 41

ERP · 37

Database · 50

Data warehouse · 28

Business productivity · 37

Accounting and finance · 16

How it works

Set up Navan in minutes, without APIs.

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 with its 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
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Navan objects to sync — Stacksync auto-detects the schema, 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
    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 database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Navan connector FAQ

What can I sync with the Navan connector?

Navan's core objects — Card Transactions, Connect Transactions, Manual Transactions, Bookings and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Navan?

Via REST (Expense API and Booking API), authenticated with 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). Changes are detected as follows — 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.. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Navan connector two-way?

Yes. Changes made in Navan propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Navan integration take to set up?

Most Navan integrations go live in minutes: authenticate Navan and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Navan data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Navan data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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
CSA STAR
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
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