Agent skill · data analytics · jeremylongshore
navan-data-sync
Synchronize Navan booking, expense, identity, and file-delivered data according to each documented source contract. Use when building durable ETL or correcting sync drift. Trigger with "Navan data sync", "Navan ETL", or "reconcile Navan feeds".
Why this skill is useful
Provides specific ETL pipeline patterns and sync strategies for Navan data that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. Requires navan account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Navan Multi-Surface Data Synchronization Overview Synchronize Navan booking, expense, identity, and file-delivered data according to each documented source contract. This workflow produces an auditable decision or artifact before any live action. Prerequisites Access to the selected tenant's current Navan Help Center and contracted integration documentation. A named business owner and data owner for the travel or expense workflow. A non-production evidence set with secrets and traveler data removed. Current Contract Do not assume bookings are weekly full refreshes, transactions are append-only, or generic webhooks exist. Record snapshot, incremental, correction, deletion, ordering, and delivery semantics independently for every enabled API, file, or managed integration. Authentication Use distinct read identities or transfer credentials per surface and tenant. Keep destination write credentials separate from Navan access and from any privileged write-back identity. Instructions 1. Build a surface ledger with contract revision, keys, timestamps, cadence, and correction semantics. 2. Capture a durable source checkpoint without advancing it before destination acknowledgement. 3. Land immutable raw records with hashes and sensitivity controls. 4. Normalize through versioned mappings while preserving source lineage. 5. Apply idempotent destination writes and quarantine unknown or conflicting records. 6. Reconcile source windows, destination acknowledgements, totals, late changes, and deletion obligations. Tool Discipline Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-data-sync