Integrations / Trigger.dev
Trigger.dev
Schedules and runs, with statuses.
Why connect it
Trigger.dev v3 has a real schedules API and a runs API with statuses, so failing scheduled tasks are visible with their run ids.
What you'll see
- Every schedule with cron and task
- Runs and failures over 7 days
- Inactive schedules shown as paused
What the credential can and cannot do
Where to get it: cloud.trigger.dev → project → API keys (the environment's secret key).
It grants: Full access to that environment's API. GitDoctor only reads schedules and runs.
It cannot: GitDoctor never triggers, cancels, or edits tasks.
Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.