Navan

Pull corporate travel and expense data out of Navan: agents list and retrieve expense and card transactions, fetch receipts for audit evidence, surface embedded travel booking details, and read custom fields to map spend into accounting systems.

7 actions API key available

Navan website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The nightly spend sync window opens after the day's transactions have posted

List Transactions pulls the day's expenses across card, manual, and repayment types by posted date

List Custom Fields maps each transaction's custom field values to the accounting system's dimensions

The agent screens for the outliers: flagged transactions, missing receipts, amounts over policy thresholds

Get Transaction Receipt attaches receipt links to every clean transaction bound for the ledger

The finance reviewer rules on the outliers, with booking details pulled inline for travel spend

Approved transactions post to the accounting system, coded by department and custom field

What This Integration Enables

Navan holds two datasets finance teams need in the same breath: what was spent and what trip it bought. This connector is read-focused by design, built on Navan's Expense API, and its job is extraction: FlowRunner agents list expense and corporate card transactions by posted-date range, retrieve full transaction detail including cardholder, department, approval status, and custom field values, pull receipt links as audit evidence, and surface the travel booking details that Navan embeds inside travel expenses. Two facts shape every workflow here, and this page states them rather than hiding them. First, the API is gated: it is an enterprise offering, and endpoints should be validated against your own credentials before production. Second, bookings are derived, not native: the public API exposes trip data only through the BOOKING field group on transactions, and the booking operations here query it that way. - Reconcile posted transactions into accounting and ERP systems on a nightly cadence - Sync corporate card spend into spreadsheets and warehouses for analysis - Forward receipt evidence into compliance and audit workflows - Attach trip context to travel spend without a dedicated bookings feed The custom fields layer is what makes the export usable rather than merely available. List Custom Fields returns the company-level dimensions your finance team configured, cost centers, project codes, billability flags, so agents map spend into the ERP the way your chart of accounts expects, not the way a generic connector guesses.

Without FlowRunner

Spend visibility arrives monthly Card and travel spend is understood at statement time, weeks after the money moved

Receipts are a chase Reconciliation stalls while someone hunts for evidence attached somewhere in the platform

Travel context is separate from cost The expense says $840; what trip, which vendor, and why live somewhere else

With FlowRunner

Spend data flows nightly Transactions land in the warehouse and the ledger on a daily cadence, coded and receipt-linked

Evidence travels with the transaction Receipt URLs ride along into accounting, so the audit trail assembles itself

Every travel expense carries its trip Booking details come embedded: vendor, travel type, confirmation, tied to the charge

Use Case Scenarios

The nightly close that feeds the ledger

Each night, the agent calls List Transactions for the prior day, respecting Navan's documented lag by querying a window that has fully settled. Custom field values map to account codes via the dictionary from List Custom Fields, receipt links attach via Get Transaction Receipt, and clean transactions become bills in [QuickBooks Online](/integrations/quickbooks). Exceptions queue for the reviewer. Month-end stops being an archaeology project because the ledger has been current all month.

Card spend analysis without the statement wait

A weekly flow calls List Card Transactions, pulling card-specific fields like card nickname and source card ID alongside amounts and merchants, and appends everything to the spend model in [Google Sheets](/integrations/google-sheets). Department heads see their teams' card burn on Monday, not at statement close. The same feed powers threshold alerts: when a single card's weekly total crosses its budget line, the agent posts the breakdown to the finance channel in [Slack](/integrations/slack).

The flagged travel expense with its trip attached

A transaction comes back flagged, large, and travel-typed. The agent calls Get Transaction with booking details included, and Get Booking surfaces the embedded trip: vendor, travel type, confirmation number. The whole picture posts to the finance channel: who traveled, where, what it cost, and the receipt link. The reviewer decides in one look instead of three systems, and the decision is recorded with the evidence that informed it.

Human-in-Loop Highlight

Every number List Transactions returns is on its way to becoming a ledger entry, and ledger entries are writes with long memories: a mis-coded department survives into board reporting, a duplicate posting inflates a cost center until someone audits it, and Navan's own documentation notes transactions can take up to 4 hours to appear, which is precisely the seam where a naive sync double-posts or misses a day. So FlowRunner agents treat the export boundary as the control point. Clean, receipt-backed, policy-passing transactions flow into accounting automatically. Anything flagged in Navan, anything over threshold, anything missing its receipt from Get Transaction Receipt, and any sync window that overlaps the settlement lag stops for the finance reviewer, who sees the transaction, its booking context, and its proposed coding together. The agent moves the data. The reviewer owns what the ledger ends up saying, because restating it later costs far more than approving it now.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

7 actions

Expenses

List Transactions Lists expense transactions of all types, card, connect, manual, repayments, fees, adjustments, filtered by a required posted-date range with optional type, approval status, and flag filters. Cursor-paginated. Data may take up to 4 hours to appear after recording.
Get Transaction Retrieves one transaction by ID with the full field set: amounts, currency, dates, cardholder, department, approval status, receipt links, and custom field values. Optionally includes the BOOKING field group for embedded trip details.
List Card Transactions Lists only corporate card transactions, adding card-specific fields such as source card ID, description, and nickname. Requires a posted-date range; cursor-paginated.
Get Transaction Receipt Retrieves receipt links for a specific transaction: metadata and URLs for attached images and documents. The evidence step behind audit and reconciliation flows.

Travel

List Bookings Lists travel bookings within a date range by querying transactions with booking details included and returning each embedded booking_details block. Derived from the Expense API, since Navan's public API has no standalone bookings endpoint.
Get Booking Retrieves trip details for a single travel expense by transaction ID: trip id, travel type, vendor, confirmation, and related fields, from the embedded BOOKING field group.

Configuration

List Custom Fields Lists the company-level custom fields configured on the Expense account, with each field's name, type, and options. The mapping key for translating custom_field_values into ERP and accounting dimensions.

Frequently Asked Questions

What can FlowRunner do with Navan?

FlowRunner agents can run List Transactions, Get Transaction, and List Card Transactions in Navan, plus 4 more actions.

Does connecting Navan to FlowRunner require OAuth?

No. Navan connects to FlowRunner with an API key, no OAuth flow required.

Can Navan trigger a FlowRunner workflow automatically?

Navan doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Navan

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us