Vercel integration

Connect your Vercel project to Trigger.dev and never run a manual deploy command again. Automatic deploys, env var sync, and atomic deployments.

What it does

Three things, all automatic:

1. Automatic deployments: Push code, Vercel deploys your app, Trigger.dev deploys your tasks. No trigger.dev deploy command, no CI/CD config to maintain.
2. Environment variable sync: Variables flow both ways. Your Vercel env vars get pulled into Trigger.dev before each build. Trigger.dev syncs API keys (like TRIGGER_SECRET_KEY) back to Vercel.
3. Atomic deployments: Your Vercel app and Trigger.dev tasks deploy in lockstep. Your app never goes live with a mismatched task version.

Atomic deployments

When atomic deployments are enabled, Trigger.dev gates your Vercel deployment until the task build completes, sets the correct TRIGGER_VERSION, then triggers a Vercel redeployment.

Environment mapping

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

Environment variable sync

Sync happens in both directions between Vercel and Trigger.dev per-environment.

Build options

• Atomic deployments: Sync Vercel and Trigger.dev deployments
• Pull env vars before build: Retrieve latest Vercel env vars before each build
• Discover new env vars: Auto-create new Trigger.dev vars when they appear in Vercel

Getting started

Connect from Trigger.dev Settings or the Vercel Marketplace. Deploy the Next.js starter app with one click.