navan-data-sync

# Navan — Data Sync ## Overview This skill provides production-grade sync strategies for Navan data. The two primary tables have fundamentally different sync models: BOOKING requires weekly full-refresh with merge-upsert logic (every record is re-imported, keyed by UUID), while TRANSACTION is incremental and append-only. Real-time use cases require webhook callbacks for event-driven processing. This skill covers all three tiers — scheduled full-refresh, incremental watermark-based sync, and real-time webhooks — along with Airbyte connector configuration and idempotent SQL upsert patterns. ## Prerequisites - Navan account with OAuth 2.0 API credentials (see `navan-install-auth`) - Destination warehouse (Snowflake, BigQuery, PostgreSQL, or Redshift) - For managed sync: Airbyte instance (Cloud or OSS) with source-navan v0.0.42+ - For webhooks: publicly accessible HTTPS endpoint for callbacks - Node.js 18+ or Python 3.8+ - Environment variables: `NAVAN_CLIENT_ID`, `NAVAN_CLIENT_SECRET`, `NAVAN_BASE_URL` ## Instructions ### Step 1: Full-Refresh Sync for BOOKING Table The BOOKING table is re-imported weekly by Navan. Every record is refreshed, so your sync must use merge-upsert logic to avoid duplicates while capturing updates. ```typescript const tokenRes = await fetch(`${process.env.NAVAN_BASE_URL}/ta-auth/oauth/token`, { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, body: new URLSearchParams({ grant_type: 'client_credentials'...