Skip to content
Data warehouse ⇄ Accounting and finance

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

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

Land the financial records from Navan in Dremio continuously, and write results back, without building or maintaining a pipeline.

Finance data belongs in the warehouse: revenue, invoices, payments, and customers joined with everything else the business measures. Getting it there usually means an extraction pipeline that breaks quietly and delivers yesterday's numbers.

Stacksync syncs Repayments, Fees, and Adjustments, Users, Card Transactions, Connect Transactions from Navan into tables in Dremio in real time, and the connection works in both directions: values computed in Dremio can be written back to fields in Navan where you want them operational. Schema changes are handled, API limits are managed, and the sync is something you configure rather than code you maintain.

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 Reverse-ETL aggregates computed over lake data out to CRMs and finance tools for business users.
  • 04 Publish operational database tables into Iceberg via Dremio so the lakehouse reflects current application state.

Common sync patterns

Write-back of computed fields

Scores or segments computed in Dremio, like payment-risk flags or customer tiers, sync back onto records in Navan where the finance team can act on them.

Queryable history for audit and reconciliation

A continuously synced copy in Dremio gives you a durable, queryable record of financial data for month-end and audit questions.

Finance analytics without ETL

Invoices, payments, and customer records from Navan arrive in Dremio as queryable tables, current within seconds instead of a day behind.

What you can sync between Dremio 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.

Dremio objects Navan objects How this pairing syncs
Spaces and folders Namespaces that organize virtual datasets and govern access. 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. Spaces and folders is specific to Dremio and Bookings to Navan — each maps to any object or custom field on the other side.
Reflections Materialized accelerations that make repeated extraction queries cheaper. Custom Fields Company metadata such as cost centers and project codes; discovered via GET and their option lists created or updated via async POST. Reflections is specific to Dremio and Custom Fields to Navan — each maps to any object or custom field on the other side.
Jobs Query execution records useful for monitoring sync workloads. Receipts Receipt images tied to each transaction; fetched read-only through presigned URLs for archival in a warehouse or document store. Jobs is specific to Dremio and Receipts to Navan — each maps to any object or custom field on the other side.
Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. Sources is specific to Dremio and Repayments, Fees, and Adjustments to Navan — each maps to any object or custom field on the other side.
Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. Physical datasets is specific to Dremio and Users to Navan — each maps to any object or custom field on the other side.
Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. 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. Virtual datasets (views) is specific to Dremio and Card Transactions to Navan — each maps to any object or custom field on the other side.

How changes propagate between Dremio 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.

Dremio Navan Interval-based propagation

DetectionStacksync polls Dremio for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL.

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

Navan Dremio 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 Dremio as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Dremio: Bounded by engine capacity and workload management rather than API rate limits.
  • 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 Dremio ⇄ Navan

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dremio and Navan.

How the Dremio and Navan connectors work

Dremio

Integration surface
Arrow Flight SQL, JDBC/ODBC, and a REST API
Authentication
Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
Change detection
Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
Capabilities
read · write
Rate limits
Bounded by engine capacity and workload management rather than API rate limits

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

    Choose tables

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

Dremio 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 429 integrations available for Dremio and Navan.

Popular · 8 of 429
All Dremio 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