Trigger.dev
Use Trigger.dev with AI apps and agents through Vercel Connect. Follow a complete setup guide for secure runtime access.
Install the skill
$ npx skills add vercel/vercel-plugin --skill vercel-connectConnect to
Use its data in agents(opens in new tab) and apps(opens in new tab)
import { getToken } from '@vercel/connect';const token = await getToken('trigger-dev/acme-trigger-dev');
Use Trigger.dev in apps and agents
Build, deploy, and manage background tasks and workflows.
Why use Vercel Connect with Trigger.dev?
Credentials on demand
Request Trigger.dev credentials only when your application or agent needs them instead of copying secrets into application code.
Access for the right subject
Keep app-scoped Trigger.dev access behind a reusable connector controlled by your team.
Centralized credential management
Manage Trigger.dev credentials in one place and retrieve them through a consistent runtime API.
Vercel-native controls
Bind connections to the projects and environments that need them while Vercel OIDC authenticates each runtime request.
Use Trigger.dev with your stack
Follow a complete setup for the Connect SDK or a supported agent framework.
Add Trigger.dev to an existing Vercel application with the Connect SDK.
Install the Connect SDK
npm install @vercel/connectCreate the Trigger.dev connector
Run these commands from the project that will use the connection.
vercel linkvercel connect create trigger-dev --name acme-trigger-devvercel env pullRequest Trigger.dev credentials
app/api/route.tsimport { getToken } from '@vercel/connect';const token = await getToken('trigger-dev/acme-trigger-dev');
