Two-way sync
Changes in Navan or Rockset instantly reflect in both systems. No stale data, no manual imports.
Keep Navan and Rockset in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Connect Transactions, Manual Transactions, Bookings, Custom Fields from Navan into tables in Rockset in real time, and the connection works in both directions: values computed in Rockset 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.
Scores or segments computed in Rockset, like payment-risk flags or customer tiers, sync back onto records in Navan where the finance team can act on them.
A continuously synced copy in Rockset gives you a durable, queryable record of financial data for month-end and audit questions.
Invoices, payments, and customer records from Navan arrive in Rockset as queryable tables, current within seconds instead of a day behind.
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 | Rockset objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Workspaces Namespaces that group collections and query lambdas per team or environment. | Bookings is specific to Navan and Workspaces to Rockset — each maps to any object or custom field on the other side. | |
| Custom Fields Company metadata such as cost centers and project codes; discovered via GET and their option lists created or updated via async POST. | Query Lambdas Named, parameterized SQL queries invoked over REST to read synced data. | Custom Fields is specific to Navan and Query Lambdas to Rockset — each maps to any object or custom field on the other side. | |
| Receipts Receipt images tied to each transaction; fetched read-only through presigned URLs for archival in a warehouse or document store. | Aliases Stable names that point at collections, used to swap datasets without changing queries. | Receipts is specific to Navan and Aliases to Rockset — each maps to any object or custom field on the other side. | |
| Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. | Integrations Managed source connections (databases, streams, object storage) feeding collections. | Repayments, Fees, and Adjustments is specific to Navan and Integrations to Rockset — 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. | Virtual Instances Isolated compute units that separate ingest from query workloads. | Users is specific to Navan and Virtual Instances to Rockset — 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. | Collections Schemaless document containers that ingested and synced records land in. | Card Transactions is specific to Navan and Collections to Rockset — each maps to any object or custom field on the other side. |
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.
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 Rockset as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Rockset for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL queries on timestamp fields.
DeliveryEach detected change is written to Navan through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Navan–Rockset connection.
Changes in Navan or Rockset instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Navan or Rockset data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Navan or Rockset record.
Track your Navan ⇄ Rockset sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Navan and Rockset.
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.
Authenticate Navan and Rockset with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Navan and Rockset 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 497 integrations available for Navan and Rockset.