Guides · devtools · Everyday developer services
Trigger.dev
Background jobs and workflows platform. Per-environment secret keys for the SDK; an access token for CI deploys.
Researched · not yet run liveLast researched 25 October 2026 · Trigger.dev · provider site
Steps
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
Sign in or create a Trigger.dev account
Sign in to Trigger.dev. If you have no account yet, you create it yourself; verapli does not create accounts.
Where: https://cloud.trigger.dev/
Create a project
Create a Trigger.dev project in the dashboard.
Create an environment secret key
On the API keys page select the project and environment, click New API key and copy it at once (shown only once) into TRIGGER_SECRET_KEY.
verapli captures
TRIGGER_SECRET_KEYhere by plain code: encrypted in your browser, never shown to AI.Where: https://cloud.trigger.dev/_/apikeys
What you end up with
| Env var | Secret | Format | What it is |
|---|---|---|---|
TRIGGER_SECRET_KEY | secret | tr_prod_sk_… | Trigger.dev secret key for one environment |
For agents
The same entry as JSON: /api/v1/entries/trigger-dev/project · requirements /api/v1/requirements/trigger-dev/project · terms /api/v1/terms/trigger-dev/project.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for Trigger.dev, and how long will it take?"
→ tools/call requirements { "provider_id": "trigger-dev/project" }Sources
- Trigger.dev docs - API keys TRIGGER_SECRET_KEY read by SDK; keys per environment (e.g. tr_prod_sk_...); API keys page cloud.trigger.dev/_/apikeys; New API key shown once; TRIGGER_ACCESS_TOKEN for trigger deploy in CI · accessed 25 October 2026 · official
- Trigger.dev pricing Free $0 with $5/month credits; Hobby $10/month with $10 credits · accessed 25 October 2026 · official
Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Trigger.dev is not affiliated with verapli.