navan-ci-integration

# Navan CI Integration ## Overview Navan has no SDK — all CI integration uses raw REST calls against `https://api.navan.com` with OAuth 2.0 client_credentials authentication. This skill generates GitHub Actions workflows that validate your Navan integration on every push: token health checks, booking data schema validation, and travel policy compliance reports. Secrets (client_id, client_secret) are stored in GitHub Actions secrets, never in code. ## Prerequisites - **Navan Admin access** to create OAuth 2.0 application credentials (Admin > API Settings) - **GitHub repo** with Actions enabled - **GitHub Secrets** configured: `NAVAN_CLIENT_ID`, `NAVAN_CLIENT_SECRET` - Navan API base URL: `https://api.navan.com` ## Instructions ### Step 1 — Store OAuth Credentials in GitHub Secrets Navigate to your GitHub repo > Settings > Secrets and variables > Actions. Add: - `NAVAN_CLIENT_ID` — from Navan Admin > API Settings - `NAVAN_CLIENT_SECRET` — from Navan Admin > API Settings ### Step 2 — Create the CI Workflow ```yaml # .github/workflows/navan-integration-check.yml name: Navan Integration Health Check on: push: branches: [main] pull_request: schedule: - cron: '0 6 * * 1' # Weekly Monday 6am UTC jobs: navan-health: runs-on: ubuntu-latest env: NAVAN_BASE_URL: https://api.navan.com steps: - uses: actions/checkout@v4 - name: Authenticate with Navan OAuth 2.0 id: auth run: | TOKEN_RESPONSE=$(curl -s -X P...