Agent skill · software engineering · jeremylongshore
navan-core-workflow-a
Implement a governed downstream booking-data workflow from Navan into an approved system. Use when consuming the Booking API or booking-data integration. Trigger with "sync Navan bookings", "ingest travel data", or "reconcile booking export".
Why this skill is useful
Adds executable scripts for managing the complete Navan travel booking lifecycle via its REST API, which is not publicly documented.
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 Booking Data Ingestion Overview Implement a governed downstream booking-data workflow from Navan into an approved system. 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 Navan publicly describes its Booking API as a way for downstream systems to access booking data. Endpoint shape, booking lifecycle states, pagination, correction behavior, and delivery cadence must come from the tenant documentation. Authentication Use a dedicated read-only integration identity or transfer credential scoped to booking data. Traveler itinerary data is personal information and must remain within the approved destination and retention boundary. Instructions 1. Define the booking fields and business decisions the destination actually needs. 2. Capture the source schema, identifiers, timestamps, lifecycle states, and correction semantics. 3. Land immutable raw evidence in an access-controlled staging area. 4. Normalize time zones, currencies, traveler references, and status without losing source values. 5. Upsert or append according to documented semantics and quarantine conflicts. 6. Reconcile counts, sums, late changes, deletions, and destination acknowledgements. 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-core-workflow-a