Real-time
Two-way sync
Changes in Navan or Splunk instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Analytics
Navan to Splunk integration — real-time, two-way sync
Keep Navan and Splunk 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 Splunk
Feed the customers, invoices, and revenue records in Navan into Splunk in real time, so dashboards and reports run on current numbers instead of last night's export.
Navan holds the financial truth: who the customers are, what they were invoiced, what they paid, and what revenue landed. Splunk is where that data is turned into dashboards, reports, and metrics, but it only reflects the world as of its last load. When the connection between them is a scheduled extract or a hand-built pipeline, analysis runs a step behind the books, and the numbers on a chart rarely match the numbers in the finance system.
Stacksync keeps Bookings, Custom Fields, Receipts, Repayments, Fees, and Adjustments in Navan in sync with Search Results, Saved Searches, Fired Alerts, KV Store Collections in Splunk, field by field and in real time. A customer, invoice, or amount created or corrected in Navan shows up in Splunk within seconds, mapped to the right record. Where Splunk keeps its own accounts or users, the flow runs both ways, so finance attributes can enrich what Splunk already tracks.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning's reporting running on yesterday's figures.
Common use cases
- 01 Push coded expense transactions into an accounting system, then set their ERP sync status in Navan so the same records are not exported twice.
- 02 Pull Bookings by date range into a database to reconcile travel reservations against Card Transactions and monitor travel-policy spend.
- 03 Ingest application, CRM, or database records into Splunk via the HTTP Event Collector so operational data lands alongside logs for correlation and dashboards.
- 04 Read and write KV Store collections to keep Splunk lookups — asset inventories, allow/deny lists, enrichment tables — in sync with an external source of truth in both directions.
Common sync patterns
Where Splunk keeps account or user records: finance attributes enrich them
Status, plan, or outstanding balance from Navan attaches to the matching account or user in Splunk, so segments and cohorts can be cut by real financial standing.
Financial records land in Splunk for reporting
Invoices, payments, and revenue from Navan flow into Splunk as they change, so dashboards are built on live figures rather than a periodic extract.
One customer key across both
A customer or account in Navan is matched to the corresponding record in Splunk, so financial numbers join cleanly to whatever Splunk already reports on.
What you can sync between Navan and Splunk
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 | Splunk 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. | Dashboards Simple XML dashboard and view definitions at /servicesNS/{owner}/{app}/data/ui/views; exported for backup and audit, or created and updated programmatically from version control. | Repayments, Fees, and Adjustments is specific to Navan and Dashboards to Splunk — 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. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Users is specific to Navan and Search Results to Splunk — 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. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Card Transactions is specific to Navan and Saved Searches to Splunk — 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. | Fired Alerts Triggered alert instances listed at /services/alerts/fired_alerts; alert configuration (conditions, schedule, actions) lives on the corresponding saved search. Landed in a database for alert-trend and detection-coverage reporting. | Connect Transactions is specific to Navan and Fired Alerts to Splunk — 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. | KV Store Collections App-scoped, MongoDB-backed key-value collections at /servicesNS/{owner}/{app}/storage/collections/data/{collection} with full CRUD and batch endpoints. Genuinely bidirectional lookup/state store — read records out or write records in. | Manual Transactions is specific to Navan and KV Store Collections to Splunk — 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. | Indexes Index inventory and settings (retention, max size, event counts) via /services/data/indexes, with create and edit; loaded into a database for capacity, retention, and data-onboarding tracking. | Bookings is specific to Navan and Indexes to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Navan and Splunk
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 Splunk 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 Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Navan Sub-second propagation
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
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.
- Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
What ships with Navan ⇄ Splunk
Connect Navan and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Navan–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Navan or Splunk 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 Splunk record.
Observability
Monitoring
Track your Navan ⇄ Splunk 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 Splunk.
How the Navan and Splunk 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.
Splunk
- Integration surface
- REST API (management API + HTTP Event Collector)
- Authentication
- HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
- Change detection
- Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
- Capabilities
- read · write · webhooks
- Rate limits
- The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
How it works
How to connect Navan to Splunk — 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.
- 01
Connect your apps
Authenticate Navan and Splunk with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Navan
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Navan and Splunk 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.
objects · Navan ⇄ SplunkCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Navan SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Navan and Splunk 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 473 integrations available for Navan and Splunk.
Popular · 6 of 473
-
Navan ⇄ Pendo -
Navan ⇄ Treasuredata -
Splunk ⇄ Rillet -
Splunk ⇄ Workday -
Splunk ⇄ Anaplan -
Splunk ⇄ Chargebee
No integrations match .
