Travel · Beta
Navan
API integration
Ship Travel features without building the integration. Full Navan API access via Proxy, normalized data through Unified APIs, and 1 MCP-ready tools for AI agents — all extensible to your exact use case.
Built for specific customer use cases. Issues are resolved quickly.
Talk to usUse Cases
Why integrate with Navan
Common scenarios for SaaS companies building Navan integrations for their customers.
Automate Navan provisioning from your HRIS platform
HR and workforce management SaaS companies can push employee directory data into Navan so new hires get instant access with the right cost center, manager approver, and travel policy assigned on day one.
Deprovision Navan access on employee offboarding
Identity and HR platforms can automatically deactivate Navan users the moment an employee is terminated upstream, revoking corporate card and booking access without manual IT intervention.
Keep org structure in sync for travel approvals
When managers, departments, or cost centers change in your customer's source of truth, your product can mirror those updates into Navan so trip approval chains and policy tiers stay accurate.
Offer Navan as a native connector in your app
Instead of building and maintaining Navan's OAuth2 flow, user schema mapping, and pagination logic yourself, ship a native Navan integration to your customers through Truto's unified directory layer.
What You Can Build
Ship these features with Truto + Navan
Concrete product features your team can ship faster by leveraging Truto’s Navan integration instead of building from scratch.
One-click Navan connection for end customers
Embed a hosted auth flow so your users can connect their Navan workspace without you handling OAuth2 token storage or refresh.
Employee directory sync into Navan
Create and update Navan user records — including name, email, department, and manager — from your product whenever upstream HR data changes.
Automated joiner-mover-leaver workflows
Trigger Navan user creation on hire, attribute updates on role change, and deactivation on termination, all driven by events in your platform.
Manager and approver hierarchy mapping
Resolve manager relationships from your source system and apply them to Navan users so travel approvals route to the correct reviewer.
Directory drift detection and reconciliation
Periodically pull Navan users via the unified directory API and surface mismatches against your customer's system of record so admins can resolve drift.
SuperAI
Navan AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
list_all_navan_users
List Navan users. Navan gates user data behind a partner/TMC entitlement that self-serve Navan API Credentials do not carry, so this method returns 403 for every credential created from Travel > Settings > Integrations. For the Navan user directory, connect the Navan SCIM integration (navanscim) instead.
Why Truto
Why use Truto’s MCP server for Navan
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 750+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
Unified APIs
Unified APIs for Navan
Skip writing code for every integration. Use Truto’s category-specific Unified APIs out of the box or customize the mappings with AI.
Unified User Directory API
Users
The User object represents a User.
How It Works
From zero to integrated
Go live with Navan in under an hour. No boilerplate, no maintenance burden.
Link your customer’s Navan account
Use Truto’s frontend SDK to connect your customer’s Navan account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Navan
Truto’s Proxy API is a 1-to-1 mapping of the Navan API. You call us, we call Navan, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Navan’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Navan on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication to Navan work through Truto?
Navan uses OAuth2. Truto handles the end-user authorization flow, token storage, and refresh, so your customers connect their Navan workspace once and your product gets a stable connection to call against.
Which Navan data is available today through Truto?
Navan is exposed through Truto's Unified User Directory API, covering employee directory records such as name, email, department, cost center, manager, and active/inactive status — the data needed to drive provisioning and approval workflows.
Can I push users into Navan, or is it read-only?
The Unified User Directory API supports both reading and writing user records, so you can provision new Navan users, update attributes like department or manager, and deactivate users from your application.
What if I need bookings, expenses, or transaction data from Navan?
Navan's bookings and expenses endpoints aren't wired up yet — those tools are built on request. Reach out to Truto with your use case and we'll prioritize the specific resources and operations you need.
How fresh is the data synced from Navan?
Truto supports scheduled syncs and on-demand fetches against Navan's REST API. You control the polling cadence per connection, and writes propagate to Navan in real time when your app makes the call.
How are Navan's custom fields and policy tiers handled?
Navan-specific attributes that don't map to the unified schema — such as assigned travel policy tier — are accessible via passthrough so you can read and write them without losing the benefits of the unified directory model.
From the Blog
Navan integration guides
Deep dives, architecture guides, and practical tutorials for building Navan integrations.
Navan
Get Navan integrated into your app
Our team understands what it takes to make a Navan integration successful. A short, crisp 30 minute call with folks who understand the problem.