Resources · Make integration

Navan Make integrationAutomate Navan with Make.

Need your Navan travel bookings somewhere other than Navan? The Navan Make integration gives you 2 modules: one pulls bookings for a date range, the other calls the Navan API directly. This guide covers the admin setup, a first scenario and the traps.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Navan Make integration do for you?

The Navan Make integration links your Navan account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules, each one a single brick such as a search or an action. With Navan, those bricks let you read booking data and reach the Navan API without writing code.

Bookings for any period, on demand. A finance lead types a start and end date somewhere, and Search Bookings returns every Navan booking in that range. Each booking arrives as a bundle, one item passed to the next module, so you can route it to a sheet or a report.

The rest of the API, same account. Navan only has two modules in Make. When you need something they do not cover, Make an API Call reaches any endpoint of the Navan API with the connection you already set up.

A travel review without exports. Place Search Bookings after the module of another app, and the booking list lands wherever your team already works. Browse the Airtable Make integration for one place to send it.

What Make cannot do here: there is no trigger, so Navan never starts a scenario by itself. Something else must kick it off, either Make's schedule or another app. Many apps also have an n8n node, so check whether Navan does, then weigh the two with n8n vs Make, and read the Make review before committing.

Connect

How do you connect Navan to Make?

  1. 01

    Create API credentials in Navan

    Sign in to Navan as an administrator, click your username, then Admin, the Travel admin tab, Settings and Integrations. Under API Credentials, click Create New, fill in a Description and click Create.

  2. 02

    Copy the two secrets

    Navan now displays a Client ID and a Client secret. Copy both right away and keep them somewhere safe: they are what Make uses to prove it may read your Navan account.

  3. 03

    Add the connection in Make

    In your scenario, add a Navan module and click Create a connection. That creates a connection: your Navan account linked to Make once, then reused by both modules. Naming it in Connection name is optional. Paste the Client ID and Client secret, and you are done.

First scenario

Your first scenario with Navan and Make

GoalWhen a new date range lands in another app, Make pulls the matching Navan bookings.

  1. 01

    Start a new scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the module of the app where the date range comes from, such as a sheet your finance team fills in.

  2. 02

    Add Search Bookings

    Click the + on the right of that first module, search for Navan and choose Search Bookings. Select the connection you created, or click Create a connection if you skipped that part.

  3. 03

    Map the dates

    In the date range of Search Bookings, map the start and end values coming from the first module. Mapping means clicking a value from the previous module instead of typing it by hand.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open the bubble above Search Bookings to read the bundles it returned, one per booking found in that range.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set Scheduling. A new scenario runs every 15 minutes by default. Pick what suits you, then switch the scenario on.

Modules

What the Navan modules do

Navan gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Navan1

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

This module opens the whole Navan API to your scenario, reusing the connection you already created, so you can reach data that Search Bookings does not return.

When to use it
choose it once you know the exact Navan endpoint you need and no listed module covers it.
Watch out
every call counts as one operation, a single run of one module that Make counts on your plan, so avoid firing it for every bundle when one call is enough.
Navan2

Search Bookings

Search

In MakeRetrieves your bookings data from Navan by date range.

You get a list of your Navan bookings for the date range you set, each one delivered as its own bundle ready to map into the next module.

When to use it
pick it whenever the question starts with a period, for example the trips of a closing month that finance wants to review.
Watch out
a search can return zero, one or many bookings, so plan for the empty case before you send the results anywhere.
Need help

Need help automating Navan with Make?

A person reads every message.

FAQ

Navan and Make: common questions

01Is the Navan Make integration free?
Yes, on the Make side. Navan is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and count usage in operations per month. Your Navan subscription is a separate matter: check the Navan pricing page, since this page gives no price for Navan itself.
02What do you need to connect Navan to Make?
A Navan account with Administrator permissions and Expense Transaction API access. Without both, Navan will not let you create the credentials Make needs. From the Admin menu, go to the Travel admin tab, then Settings and Integrations, and create a new API credential. Navan shows a Client ID and a Client secret: copy them. In Make, click Create a connection on a Navan module, optionally name it, and paste the two values. If Navan asks for a callback URI, use the one given in the Make documentation.
03Can the Navan Make integration react in real time?
No. Navan has no trigger in Make, so no module watches Navan for you and nothing fires the moment a trip is booked. A scenario still needs a starting point. The first option is Make's own schedule: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that. The second is to start with a trigger from another app, then place Search Bookings after it to fetch the bookings for the dates that app provides.
04What if a Navan module is missing in Make?
Use Make an API Call. It sends any request the Navan API accepts, with the same connection as Search Bookings, so you do not need a second login. You will need the Navan API documentation to know which endpoint to call and what it expects. Also keep in mind that the Make help page for Navan is flagged as AI-generated from Navan's own documentation and may contain mistakes, so double check important details with Navan before relying on them.
05Should you use Make or n8n for Navan?
It depends on what the rest of your stack runs on. In Make, Navan comes with two modules, Search Bookings and Make an API Call, both usable from the Free plan, which is enough to pull bookings by period and to reach the rest of the API. Many apps also have an n8n node, but this page does not confirm one for Navan, so check that first. If your other automations already live in one tool, keeping Navan there usually saves you a second set of connections.