Vercel Integration

The Vercel integration automates Trigger.dev task deployments whenever code is deployed to Vercel.

How It Works

Installation

Option 1: From Trigger.dev Dashboard

1. Dashboard → Integrations → Vercel
2. Authorize Vercel
3. Select your Vercel project
4. Map environments

Option 2: From Vercel Marketplace

1. Vercel Marketplace → search "Trigger.dev"
2. Add integration
3. Follow authorization flow

Environment Variable Sync

Variables flow bidirectionally:

Direction	What syncs
Vercel → Trigger.dev	Your app's env vars (per environment)
Trigger.dev → Vercel	TRIGGER_SECRET_KEY, TRIGGER_API_URL

Excluded from sync:

• Variables managed by Trigger.dev itself
• Sensitive/secret-type variables (Vercel API limitation)

Atomic Deployments

When atomic deployments are enabled:

1. Your Vercel deployment is held (not live) while Trigger.dev builds tasks
2. Once task build completes, Trigger.dev sets TRIGGER_VERSION in Vercel
3. Vercel redeploys with the correct version — app and tasks stay in sync

This prevents the app from running with mismatched task code.

Environment Mapping

Vercel environment	Trigger.dev environment
Production	Production
Preview	Preview / Staging
Development	Development

Per-Environment Settings

Administrators can configure per-environment:

• Enable/disable atomic deployments
• Enable/disable environment variable pulling
• Auto-discovery of new variables

Disconnecting

Disconnect from either platform at any time. This:

• Stops automatic deployments
• Stops variable syncing
• Does not affect existing deployments or variables

Manual Deployment (Fallback)

If the integration is not active, deploy manually:

npx trigger.dev@latest deploy

Or via GitHub Actions — see CI/CD guide.