Skip to content
Human resources ⇄ Accounting and finance

Namely to Navan integration — real-time, two-way sync

Keep Namely and Navan 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 Namely and Navan

Keep the employee, department, and cost records that Navan and Namely share consistent in real time, so the finance system and the people system stop drifting apart.

Navan runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Namely runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Custom Fields, Receipts, Repayments, Fees, and Adjustments, Users in Navan with Job Titles, Job Tiers, Groups, Teams in Namely bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

Common use cases

  • 01 Pull Bookings by date range into a database to reconcile travel reservations against Card Transactions and monitor travel-policy spend.
  • 02 Sync Users and department mappings from an HRIS into reporting tables so every transaction is attributed to a cost center and manager.
  • 03 Feed Namely Reports as JSON into a database on a schedule for roster, turnover, and diversity dashboards without manual CSV exports.
  • 04 Provision or deprovision accounts in an IdP or directory when a Profile's user_status or start_date changes, and write the resulting user ID and email back onto the Profile.

Common sync patterns

New person becomes a known record in finance

When someone is added in Namely, a matching employee or payee record appears in Navan, ready for payroll, expenses, or cost allocation without anyone rekeying the details.

One employee identity

A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.

Department and cost-center alignment

The org structure maintained in Namely keeps the departments or cost centers in Navan current, so spend and headcount roll up the same way.

What you can sync between Namely and Navan

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.

Namely objects Navan objects How this pairing syncs
Teams Teams and team categories a Profile belongs to; read and written for org-chart and provisioning workflows. Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. Teams is specific to Namely and Repayments, Fees, and Adjustments to Navan — each maps to any object or custom field on the other side.
Reports Saved Namely reports returned as JSON snapshots that update instantly; read-only feeds for headcount and roster analytics. Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. Reports is specific to Namely and Users to Navan — each maps to any object or custom field on the other side.
Profile Fields Metadata describing standard and company-defined custom field sections; read to discover schema and generate mappings. 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. Profile Fields is specific to Namely and Card Transactions to Navan — each maps to any object or custom field on the other side.
Events Home-feed items such as announcements, birthdays, anniversaries, and new arrivals; typically read-only into comms tools. Connect Transactions External and personal card feed matched into Navan; retrieved read-only and coded with custom-field values through the transaction update endpoint. Events is specific to Namely and Connect Transactions to Navan — each maps to any object or custom field on the other side.
Profiles The core employee record (personal, job, contact, and compensation fields); synced two-way via GET/POST/PUT with updated_at driving incremental polling. Manual Transactions Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan. Profiles is specific to Namely and Manual Transactions to Navan — each maps to any object or custom field on the other side.
Job Titles Job title definitions; read and written so titles stay aligned with an HRIS, directory, or reporting dimension. 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. Job Titles is specific to Namely and Bookings to Navan — each maps to any object or custom field on the other side.

How changes propagate between Namely and Navan

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.

Namely Navan Interval-based propagation

DetectionStacksync polls Namely for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks.

DeliveryEach detected change is written to Navan through its API, with automatic retries and rate-limit backoff.

Navan Namely 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 Namely through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Namely: Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
  • 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.
What ships with Namely ⇄ Navan

Connect Namely and Navan for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Namely–Navan connection.

Real-time

Two-way sync

Changes in Namely or Navan instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Namely or Navan 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 Namely or Navan record.

Observability

Monitoring

Track your Namely ⇄ Navan sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Namely and Navan.

How the Namely and Navan connectors work

Namely

Integration surface
REST API (JSON over HTTPS)
Authentication
OAuth 2.0 authorization-code grant, or a personal access token sent as a Bearer token; all calls run over HTTPS against https://{subdomain}.namely.com/api/v1
Change detection
No webhooks; integrations poll GET endpoints and compare the updated_at / created_at timestamps on Profiles and related objects to detect changes
Capabilities
read · write
Rate limits
Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.

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.
How it works

How to connect Namely to Navan — 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.

  1. 01

    Connect your apps

    Authenticate Namely and Navan with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Namely connected
    Navan connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Namely and Navan 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Namely ⇄ Navan
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Namely Navan
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Namely and Navan 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 398 integrations available for Namely and Navan.

Popular · 8 of 398
All Namely integrations All Navan integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own