From 0db50bdb304d39a064dde113b03142305969124b Mon Sep 17 00:00:00 2001 From: Prateet Tiwari Date: Sat, 2 May 2026 23:40:44 +0530 Subject: [PATCH] docs: clarify trigger.config.ts requirement in Vercel integration --- docs/vercel-integration.mdx | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/vercel-integration.mdx b/docs/vercel-integration.mdx index 3c2cc1b9665..905f289e45b 100644 --- a/docs/vercel-integration.mdx +++ b/docs/vercel-integration.mdx @@ -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. + + Make sure you've completed the [Quickstart](/quickstart) first, including creating your `trigger.config.ts` file. + + ## Installation You can connect Vercel from two entry points: @@ -89,6 +93,18 @@ You can connect Vercel from two entry points: from the repo root. +## 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. +``` + +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: