Skip to content
Database ⇄ Accounting and finance

Azure Cosmos DB to Navan integration — real-time, two-way sync

Keep Azure Cosmos DB 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 Azure Cosmos DB and Navan

Work with Navan's financial data straight from Azure Cosmos DB: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Connect Transactions, Manual Transactions, Bookings, Custom Fields from Navan into Items (JSON documents), Partition keys, Change feed entries, Stored procedures and triggers in Azure Cosmos DB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Azure Cosmos DB, and rows your code writes or updates flow back into Navan with validation, so the finance system stays the system of record.

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 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
  • 04 Consolidate documents from multiple containers into a single reporting store.

Common sync patterns

Write back safely

Updates written to the synced tables in Azure Cosmos DB propagate into Navan, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Navan appear in Azure Cosmos DB as row changes, so you can trigger downstream logic with the database tooling you already use.

Query finance data like any other data

Customers, invoices, and payments from Navan live in Azure Cosmos DB as regular tables or collections your team can join, index, and query.

What you can sync between Azure Cosmos DB 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.

Azure Cosmos DB objects Navan objects How this pairing syncs
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. Stored procedures and triggers is specific to Azure Cosmos DB and Users to Navan — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. 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. Databases is specific to Azure Cosmos DB and Card Transactions to Navan — each maps to any object or custom field on the other side.
Containers The unit of partitioning and throughput; each container maps to a synced collection. Connect Transactions External and personal card feed matched into Navan; retrieved read-only and coded with custom-field values through the transaction update endpoint. Containers is specific to Azure Cosmos DB and Connect Transactions to Navan — each maps to any object or custom field on the other side.
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Manual Transactions Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan. Items (JSON documents) is specific to Azure Cosmos DB and Manual Transactions to Navan — each maps to any object or custom field on the other side.
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. 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. Partition keys is specific to Azure Cosmos DB and Bookings to Navan — each maps to any object or custom field on the other side.
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. Custom Fields Company metadata such as cost centers and project codes; discovered via GET and their option lists created or updated via async POST. Change feed entries is specific to Azure Cosmos DB and Custom Fields to Navan — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB 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.

Azure Cosmos DB Navan Sub-second propagation

DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.

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

Navan Azure Cosmos DB 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 applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.

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.
What ships with Azure Cosmos DB ⇄ Navan

Connect Azure Cosmos DB and Navan for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Navan.

How the Azure Cosmos DB and Navan connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

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 Azure Cosmos DB 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 Azure Cosmos DB 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
    Azure Cosmos DB connected
    Navan connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Azure Cosmos DB 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
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

Related integrations

Every pair below is a real-time, two-way sync. Search all 433 integrations available for Azure Cosmos DB and Navan.

Popular · 7 of 433
All Azure Cosmos DB 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