Resources · Zapier integration

Navan Zapier integrationAutomate Navan with Zapier.

The Navan Zapier integration is small: 1 trigger, 0 actions and 1 search, all about bookings on the travel and expense platform. Zapier can read new bookings and look up existing ones, but it cannot write anything back into Navan.

Beta app Zapier still marks this integration as beta.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Navan Zapier integration can and cannot do

Navan handles corporate travel and expenses. Zapier connects it to your other tools through a Zap: an automation made of one trigger (the event that starts it) and one or more actions (what it then does for you). With Navan, the only event on offer is a new booking, and Navan itself never appears as an action.

A booking log nobody has to maintain. New Booking starts a Zap for each booking created in Navan, and the next step writes it wherever your team keeps track: a sheet, a database, a shared list. Its official description says it can be narrowed down by booking type or booking status, so one Zap can keep only what matters.

A heads-up when someone books. The same trigger can feed a message in your team chat or an email, so the people who need to know about a trip hear about it without opening Navan.

A lookup inside a bigger Zap. Find Bookings searches existing bookings in Navan. Since a Zap cannot start with a search, it sits after a trigger from another app and hands what it found to the following steps.

What Zapier does not do here: there is no action at all, so a Zap cannot create, change or cancel a booking, and nothing touches expenses. Zapier also flags this integration as beta. The trigger is a polling one, so it is not instant. If Navan on Make is an option, see our Navan Make integration page.

Vocabulary

Zapier words, in plain English

Seven words are enough for the rest of this page. One line each, then they are used as they are.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. For Navan, it is New Booking, and Zapier waits for nothing else.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, in another app here.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan counts those, not the checks.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only the ones it has not seen.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found.
Cost

What a Navan Zap costs

Navan is not a premium app: it runs on the free plan. Since it has no action, the tasks you spend are those of the other apps in the Zap.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

The trigger never costs a task, and Zapier checking Navan for new bookings costs nothing either, however often it looks. Each action that succeeds counts once; one that fails is not counted. The free plan gives 100 tasks a month and Zaps of two steps, which is exactly New Booking plus one action. A filter, a second action or Find Bookings makes the Zap multi-step, which needs a paid plan. How often New Booking is checked depends on the plan, as the grid shows.

Connect

Connect Navan to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Navan account linked once, then reused by every step that uses Navan.

  2. 02

    Pick Navan

    Type Navan in the search box of the dialog, select it and click Add connection. A new tab opens, and that is where the sign-in of the next step takes place.

  3. 03

    Sign in and grant access

    Sign in to Navan in that tab and give Zapier access to the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

First Zap

Your first Navan Zap: a booking log with a heads-up

GoalEach new Navan booking is added to your tracking sheet, then announced in your team chat.

  1. 01

    Set the trigger

    Create a Zap, pick Navan and the New Booking event, then your Navan connection. If you only want some bookings, look at the trigger's own options before reaching for a filter.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent bookings of the connected account, so the next steps are mapped on a real one.

  3. 03

    Add the row

    Add your spreadsheet as the first action, then map the booking details you care about into its columns. Test the step and read what came back.

  4. 04

    Add the message

    Click the plus icon, add your team chat and write the message with the booking details. Two actions make a multi-step Zap, which needs a paid plan.

  5. 05

    Publish

    Click Publish to switch the Zap on. Only bookings created from then on will start it. For a guided build on your own account, see our Zapier training.

Triggers

The Navan trigger

1 event starts a Zap when something happens in Navan. Zapier checks for them at the interval your plan allows.

1

New Booking

Polling trigger

In Zapier“Triggers when a new booking is created in Navan, optionally filtered by booking type or booking status.”

Each booking created in Navan reaches your Zap, with its details ready for the next step. The official description adds that the trigger can be narrowed by booking type or booking status, so a single Zap can keep only one kind of trip, or only bookings in a given state. It is the only door into Navan that Zapier offers.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
keep a travel log without anyone copying bookings by hand.
Watch out
bookings made before the Zap was published are never picked up.
Searches

The Navan search

1 search step looks for data that already exists in Navan, so a later step can use it.

A search step looks up something that already exists in an app and passes it to the next steps. Searches sit at the bottom of the action list, under SEARCH. Adding one makes the Zap multi-step, so it needs a paid plan.

1

Find Bookings

Search

In Zapier“Finds bookings in Navan matching the given filters.”

Looks through existing Navan bookings that match the filters you give it, and hands what it found to the steps that follow.

When to use it
a Zap started by another app needs booking details from Navan before it writes or sends anything.
Watch out
several bookings can match, so set the multiple results option on purpose.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there, and the steps that relied on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Navan has no action to create anything, and Find Bookings offers no such variant.
  3. If multiple search results are found?
    Three ways out when several bookings match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When a Navan Zap breaks

Zapier attaches no help article to Navan and no app-specific limit is published. What can go wrong comes from how Zapier works in general.

Four cases apply to a Navan Zap. If one still misbehaves after you have checked them, see our Zapier troubleshooting guide.

  • No look back

    A Zap only reacts to what happens after you switch it on. Bookings that already existed are never picked up; moving them is a separate job.
  • The wait between checks

    New Booking is a polling trigger: Zapier looks at an interval set by your plan, 15 minutes on the free one, so the Zap never runs the moment a booking is made.
  • A sudden flood

    After a bulk import or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection.
  • The same booking twice

    Zapier keeps track of what it has already seen on a polling trigger, so the same booking does not start the Zap twice.
Need help

Need help automating Navan with Zapier?

A person reads every message.

FAQ

Navan and Zapier: the questions people ask

01Is the Navan Zapier integration free?
Yes. Navan is not a premium app, so it runs on the free plan, which gives 100 tasks a month and an unlimited number of Zaps of two steps each: one trigger, one action. New Booking followed by a row in a sheet fits. Find Bookings does not, because any search makes the Zap multi-step, and so do a filter and a second action: those need a paid plan. Since Navan has no action, every task you spend goes to the other apps of the Zap.
02How many tasks does a Navan Zap use?
One per successful action, and nothing for the trigger. Zapier checking Navan for new bookings costs nothing, however often it looks. A Zap that logs each booking in a sheet uses one task per booking; the Zap on this page, which also sends a message, uses two. An action that fails is not counted against the plan. Zapier also notes that a few apps and a few actions take more than one task when they complete.
03Does a Navan Zap start the moment a booking is made?
No. New Booking is a polling trigger: Zapier asks Navan for new bookings at an interval set by your plan, every 15 minutes on the free plan, 2 on Professional, 1 on Team and Enterprise. A booking made right after a check waits for the next one. On paid plans the frequency can be changed, and a check can be run by hand from the editor when you are testing.
04What does it take to connect Navan to Zapier?
An account on Navan, plus read or write access on anything you do not own yourself and want the Zap to touch. Then open Apps in Zapier, click + Add connection, pick Navan, sign in in the tab that opens and grant access. The connection is reused by every Navan step. Since the integration has no action, Zapier only reads bookings here and never writes back into Navan. The test of New Booking then brings back the three most recent bookings of the connected account.
05Can Zapier create or change a Navan booking?
No. The Navan integration has no action at all: Zapier can notice new bookings with New Booking and look up existing ones with Find Bookings, nothing more. Creating, changing or cancelling a trip stays in Navan. In practice, Navan works as a source for your Zaps, never as a destination, and that is worth knowing before you plan a workflow that expects to write travel or expense data back into the platform.
06What if the Navan operation you need is not listed?
Check the Navan page on Zapier, which shows the current triggers, actions and searches. Today that is one trigger and one search, both about bookings; nothing covers expenses or writing data back. If what you want is close, a filter after New Booking or a Find Bookings step inside another Zap may be enough. If not, compare how the same need is handled by another automation tool before you build around the gap.
07Zapier, Make or n8n for Navan?
Pick on criteria, not on a ranking. On Zapier, the question is whether one polling trigger and one search cover your need, and whether the plan's interval is quick enough for how fast people need to know about a booking. Then look at cost: each successful action is a task, and a search or filter means a paid plan. Ask the same three questions, operations available, delay before a Zap starts, cost per run, of the other tools.