Agent skill · software engineering · jeremylongshore
navan-deploy-integration
Deploy a Navan integration with tenant isolation, canary controls, and reversible data flow. Use when releasing an API, file, identity, or finance connector. Trigger with "deploy Navan integration", "release Navan connector", or "canary Navan sync".
Why this skill is useful
Provides deployment checklists and specific API commands for integrating Navan with ERP and HRIS systems that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq 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 Integration Deployment Overview Deploy a Navan integration with tenant isolation, canary controls, and reversible data flow. 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 Deployment binds the application adapter to a documented Navan surface and an approved destination. Separate ingestion, normalization, publication, and write-back so each can stop without losing evidence. Authentication Inject a production secret by reference at runtime; bind tenant, host, scope, destination, and environment. Verify revocation and break-glass procedures before traffic. Instructions 1. Pin the reviewed artifact, contract revision, and configuration manifest. 2. Deploy dark with network or scheduling disabled. 3. Verify secret binding, egress allowlist, storage, redaction, and alert routing. 4. Enable a bounded tenant/window canary and collect reconciliation evidence. 5. Increase scope only after thresholds and owner review pass. 6. Keep rollback, replay protection, checkpoints, and raw evidence until acceptance. 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 Production enablement, egress, data movement, scheduling, scope expansion, and write-back require explicit service and data-owner approval. Error Handling Stop on tenant or destination mismatch. Do not roll forward through unexplained count or total drift. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-deploy-integration