Skip to content

fix: clarify trigger.config.ts requirement in Vercel integration #3512

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

Closed
Prateet-Github wants to merge 1 commit into from
+16 −0
Closed

fix: clarify trigger.config.ts requirement in Vercel integration #3512

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
16 changes: 16 additions & 0 deletions docs/vercel-integration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ This eliminates the need to manually run the `trigger.dev deploy` command or mai
well, since Trigger.dev builds your tasks from your GitHub repository.
</Note>

<Note>
Make sure you've completed the [Quickstart](/quickstart) first, including creating your `trigger.config.ts` file.
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot May 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Broken documentation link: /quickstart should be /quick-start

The new <Note> links to /quickstart, but the actual page file is docs/quick-start.mdx and the navigation in docs/docs.json:26 lists it as "quick-start". There is no redirect from /quickstart to /quick-start in the redirects section of docs/docs.json:618-747. Other docs that link to this page use the correct /quick-start path (e.g., docs/introduction.mdx:9 uses href="/quick-start" and docs/guides/ai-agents/claude-code-trigger.mdx:14 uses /quick-start). This will result in a 404 for users clicking the link.

Suggested change
Make sure you've completed the [Quickstart](/quickstart) first, including creating your `trigger.config.ts` file.
Make sure you've completed the [Quickstart](/quick-start) first, including creating your `trigger.config.ts` file.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

</Note>

## Installation

You can connect Vercel from two entry points:
Expand Down Expand Up @@ -89,6 +93,18 @@ You can connect Vercel from two entry points:
from the repo root.
</Warning>

## Required Trigger Config

Make sure your project includes a `trigger.config.ts` file in the root of your repository.

Trigger.dev looks for this file by default to configure your triggers. If it's missing, you may see an error like:

```
Error: The trigger config file was not found. By default, we look for a trigger.config.ts file in the root of your repository.
```
Comment on lines +102 to +104
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot May 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚩 Error message in 'Required Trigger Config' section may not match actual CLI output

The error message shown at docs/vercel-integration.mdx:103 (Error: The trigger config file was not found. By default, we look for a trigger.config.ts file in the root of your repository.) appears to be a paraphrased/fabricated error message rather than one copied from the actual CLI or build system. I was unable to find this exact string in the codebase. If a user encounters a different error message in practice, this could cause confusion. However, the general guidance is correct — a missing trigger.config.ts will cause build failures.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.


If your config file is located in a different directory, you can specify its path in your project's build configuration settings.

## Environment variable sync

The integration syncs environment variables in both directions:
Expand Down