Skip to content

docs: Vercel integration – marketplace link, Build options, Root Directory warning #3097

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
isshaddad merged 5 commits into from
Feb 20, 2026
Merged

docs: Vercel integration – marketplace link, Build options, Root Directory warning #3097

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ff26fdb
add link to vercel marketplace
isshaddad Feb 19, 2026
609a15e
added info regarding build options
isshaddad Feb 19, 2026
8e0a3a9
added vercel root directory warning
isshaddad Feb 19, 2026
7c91341
coderabbit changes
isshaddad Feb 19, 2026
b931ffb
coderabbit changes pt2
isshaddad Feb 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docs/vercel-integration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ You can connect Vercel from two entry points:
<Steps>

<Step title="Install the integration">
Find Trigger.dev on the Vercel Marketplace and install it. This will redirect you to Trigger.dev to complete setup.
Install the [Trigger.dev integration from the Vercel Marketplace](https://vercel.com/marketplace/trigger). This will redirect you to Trigger.dev to complete setup.
</Step>

<Step title="Select your Trigger.dev organization and project">
Expand All @@ -69,6 +69,10 @@ You can connect Vercel from two entry points:
When installing from the Vercel Marketplace, default build settings are applied automatically. You can adjust them later in your project settings.
</Note>

<Warning>
**Vercel Root Directory:** If your Vercel project uses a **Root Directory** (e.g. you deploy a single subfolder such as `app` or `web`), you may see "The specified Root Directory does not exist" after connecting the integration. Use the **repository root** (leave Root Directory empty) in your Vercel project settings instead. Trigger.dev always builds from the repo root; point to your app or tasks in a subfolder by setting the **Trigger config file** path (and other [Build options](#build-settings)) in your Trigger.dev project configuration.
</Warning>

## Environment variable sync

The integration syncs environment variables in both directions:
Expand Down Expand Up @@ -124,6 +128,8 @@ You can configure the following settings per-environment from your project's Ver
- **Pull env vars before build**: When enabled, Trigger.dev pulls the latest environment variables from Vercel before each build. Enabled for production, staging, and preview by default.
- **Discover new env vars**: When enabled, new environment variables found in Vercel that don't yet exist in Trigger.dev are created automatically during builds. Only available for environments that also have env var pulling enabled. Enabled for production, staging, and preview by default.

To change build options that would normally go in `trigger.config.ts` (such as [extensions](/config/config-file#extensions) or other build configuration), use **Build options** on your project's configuration page in the Trigger.dev dashboard.

## Disconnecting

You can disconnect the Vercel integration from either side:
Expand Down