Agent skill · product strategy · jeremylongshore
navan-reference-architecture
Design a Navan integration architecture with explicit trust, data, identity, and accounting boundaries. Use when building a multi-system travel or expense flow. Trigger with "design Navan architecture", "Navan integration diagram", or "Navan data platform".
Why this skill is useful
Provides a detailed architecture for integrating with the Navan API, including specific layers and components that the AI wouldn't generate on its own.
What it needs
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 Governed Integration Architecture Overview Design a Navan integration architecture with explicit trust, data, identity, and accounting boundaries. 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 A durable design separates vendor access, intake, immutable staging, normalization, policy, publication, write-back, reconciliation, and audit. It supports the tenant's actual API, SFTP, SCIM, SSO, or direct-integration contracts without assuming one universal transport. Authentication Place secrets at the ingress boundary, bind each identity to one tenant and purpose, and keep administrative, ingestion, and write-back privileges separate. Instructions 1. Inventory Navan surfaces, owners, data classes, consumers, and side effects. 2. Draw trust zones and every network, storage, AI, and human boundary. 3. Define canonical identifiers, money, time, lifecycle, and lineage models. 4. Add queues, checkpoints, deduplication, quarantine, and reconciliation. 5. Specify redaction, retention, encryption, access, deletion, and incident controls. 6. Document scaling, failure, deployment, rollback, and contract-upgrade paths. 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. Approval Boundaries New processors, sensitive destinations, cross-border flows, AI/MCP access, write-back, production identities, and retention changes require architecture and data-owner approval. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-reference-architecture--ff05ca