VC
Vercel
Provider Setup

Connect Vercel

ConfigTrace connects to Vercel using an account-level API token. It monitors project settings, custom domains, environment variable metadata, and deployment configuration — without reading environment variable values, build logs, or deployed code.

On this page
  1. Prerequisites
  2. Step 1 — Create an API token
  3. Step 2 — Connect in ConfigTrace
  4. Step 3 — Run your first sync
  5. What ConfigTrace monitors
  6. What ConfigTrace never reads

Prerequisites

  • →A Vercel account with access to the projects you want to monitor
  • →Permission to create access tokens
  • →A ConfigTrace workspace (owner or admin role)

Step 1 — Create an API token

  1. 1
    Open tokens page
    Go to vercel.com/account/tokens.
  2. 2
    Create the token
    Click "Create". Give it a name like ConfigTrace (read-only) and set an expiry.
  3. 3
    Copy the token
    Click "Create token" and copy the value.
ℹ
Vercel API tokens are account-scoped. If you're on a team, the token will have access to all projects the account can see. ConfigTrace will only monitor the specific project you configure in the integration.

Step 2 — Connect in ConfigTrace

  1. 1
    Open Integrations
    In the ConfigTrace sidebar, click Integrations, then click Connect on the Vercel card.
  2. 2
    Paste your API token
    Paste your API token.
  3. 3
    Scope to a project
    Enter the project name or project ID to scope the integration to a single project.
  4. 4
    Save integration
    Click Save integration.

Step 3 — Run your first sync

Click Sync Now. The first sync captures your project settings, domain configuration, and environment variable names as a baseline.

What ConfigTrace monitors

✓ Reads (configuration metadata)
  • ✓Project settings: framework, root directory, build command, output directory
  • ✓Custom domains: domain names, redirect configuration, SSL status
  • ✓Environment variable names and their target environments (production/preview/development) — not values
  • ✓Deployment protection settings
  • ✓Team and project access settings
  • ✓Git integration settings (branch, connected repo name)
✕ Never reads
  • ✕Environment variable values
  • ✕Deployed code or build output
  • ✕Build logs or runtime logs
  • ✕Serverless function code
  • ✕Edge config values
  • ✕Customer data served by deployments

What ConfigTrace never reads

⚠
ConfigTrace tracks environment variable names and their target environments to detect when variables are added, removed, or reassigned. It never reads or stores the actual values.

For a full breakdown across all providers, see the Data Access & Permissions reference.