Individual skill
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".
plugins/saas-packs/navan-pack/skills/navan-reference-architecture/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- navan Declared skill tag
- architecture Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,825 bytesreferences/official-docs.mddoc · 1,149 bytes
Read excerpt
# 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.