Skip to content
Accounting and finance ⇄ Database

Navan to Scaleway Postgres integration — real-time, two-way sync

Keep Navan and Scaleway Postgres 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 Navan and Scaleway Postgres

Work with Navan's financial data straight from Scaleway Postgres: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Bookings, Custom Fields, Receipts, Repayments, Fees, and Adjustments from Navan into Tables, Views, Materialized views, Schemas in Scaleway Postgres and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Scaleway Postgres, and rows your code writes or updates flow back into Navan with validation, so the finance system stays the system of record.

Common use cases

  • 01 Push coded expense transactions into an accounting system, then set their ERP sync status in Navan so the same records are not exported twice.
  • 02 Pull Bookings by date range into a database to reconcile travel reservations against Card Transactions and monitor travel-policy spend.
  • 03 Sync production tables from Scaleway Postgres into a CRM so sales and support see live product usage on customer records
  • 04 Run a two-way sync between Scaleway Postgres and SaaS tools so edits made in either system converge on the same rows

Common sync patterns

Query finance data like any other data

Customers, invoices, and payments from Navan live in Scaleway Postgres as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on Scaleway Postgres; Stacksync handles the API calls, rate limits, and retries against Navan.

Write back safely

Updates written to the synced tables in Scaleway Postgres propagate into Navan, so automations can create or correct finance records without custom integration code.

What you can sync between Navan and Scaleway Postgres

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.

Navan objects Scaleway Postgres objects How this pairing syncs
Manual Transactions Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan. Schemas Namespace tables so multiple applications or environments can be synced selectively. Manual Transactions is specific to Navan and Schemas to Scaleway Postgres — each maps to any object or custom field on the other side.
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. Sequences Generate primary keys; sync tooling must respect them when writing rows. Bookings is specific to Navan and Sequences to Scaleway Postgres — each maps to any object or custom field on the other side.
Custom Fields Company metadata such as cost centers and project codes; discovered via GET and their option lists created or updated via async POST. Columns Postgres-native types, including JSONB and arrays, are mapped to fields in the paired system. Custom Fields is specific to Navan and Columns to Scaleway Postgres — each maps to any object or custom field on the other side.
Receipts Receipt images tied to each transaction; fetched read-only through presigned URLs for archival in a warehouse or document store. Tables Primary sync unit; each table maps to an object or table on the other side of the sync. Receipts is specific to Navan and Tables to Scaleway Postgres — each maps to any object or custom field on the other side.
Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. Views Read-only sources for shaping data before it leaves the database. Repayments, Fees, and Adjustments is specific to Navan and Views to Scaleway Postgres — each maps to any object or custom field on the other side.
Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. Materialized views Precomputed result sets that can be read on a schedule for downstream syncs. Users is specific to Navan and Materialized views to Scaleway Postgres — each maps to any object or custom field on the other side.

How changes propagate between Navan and Scaleway Postgres

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.

Navan Scaleway Postgres 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 applied to Scaleway Postgres as a row-level write, with types converted between the two schemas.

Scaleway Postgres Navan Sub-second propagation

DetectionChanges in Scaleway Postgres are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication where the managed instance permits it.

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

Rate-limit considerations

  • 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.
  • Scaleway Postgres: Throughput is bounded by instance size and connection limits rather than API quotas.
What ships with Navan ⇄ Scaleway Postgres

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Navan and Scaleway Postgres connectors work

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.

Scaleway Postgres

Integration surface
SQL wire protocol (PostgreSQL)
Authentication
Database credentials (username/password over TLS)
Change detection
Log-based CDC via PostgreSQL logical replication where the managed instance permits it; otherwise timestamp or query-based polling
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by instance size and connection limits rather than API quotas
How it works

How to connect Navan to Scaleway Postgres — 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 Navan and Scaleway Postgres 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
    Navan connected
    Scaleway Postgres connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Navan and Scaleway Postgres 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 · Navan ⇄ Scaleway Postgres
    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
    Navan Scaleway Postgres
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Navan and Scaleway Postgres 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
CSA STAR
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 438 integrations available for Navan and Scaleway Postgres.

Popular · 7 of 438
All Navan integrations All Scaleway Postgres 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