Trigger.dev integration: connect tasks, runs and queues to Polylane

Connect Trigger.dev tasks, runs, schedules and queues to Polylane with an environment key. Investigate failed runs alongside deployment and queue state.

Get started for free

How to set up Trigger.dev

Open the production or staging environment’s API Keys in Trigger.dev. Create an environment secret key using the No restrictions preset.
Paste the key into Polylane and connect. The key identifies its project and environment; production and staging each become a separate account.
For alerts, add a webhook on the environment’s Alerts page using the account Settings webhook URL. Select Task run failure, Deployment failure and Deployment success; paste the webhook signing secret into Polylane’s Webhooks card.

Permissions and access

The No restrictions preset is required because the project identity endpoint rejects restricted presets. Trigger only, Observer, Deploy only, Task operator and Variables only keys cannot connect. Despite that credential capability, Polylane only reads: it starts no tasks, replays no runs, pauses no queues and reads no variables. Dev and preview keys are not supported for the persistent account connection.

Discovery, refresh and the connected view

The environment, deployment, tasks, schedules and queues refresh every 15 minutes. Tasks found in runs but absent from the current version remain mapped and flagged. Connecting an environment enables its monitoring; the account settings monitoring toggle can turn checks off. Failed-run webhooks open issues, and successful deployments resolve deployment alerts.

Example workflow

Investigate a failed scheduled task by comparing the run’s failure with the current deployment and queue state. Check whether that task disappeared from the current version but still has scheduled work or recent runs. The retained task node makes that version mismatch visible instead of losing the task when discovery refreshes.

Disconnect and revoke access

Disconnect the environment in Polylane and revoke its secret key in Trigger.dev. Remove the alert webhook if it should no longer deliver events.

Provider credentials and Polylane’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.

In the graph.

Every Trigger.dev resource Polylane picks up sits in the graph with its connections, config and history.

Environment

Task

Schedule

Queue

Deployment

Tools for the investigation.

What Polylane can do with Trigger.dev while it investigates. Every call is recorded in the transcript.

Trigger.dev Polylane MCP

triggerdevRuns List Trigger.dev runs with filters, retrieve one run with its attempts, or read the error groups failed runs fold into
triggerdevRunTelemetry Read a Trigger.dev run's trace tree or its log events
triggerdevQuery Query Trigger.dev run history with TRQL, or read its schema and dashboard queries
triggerdevInventory Read what a Trigger.dev environment is made of: deployments and the current one, bulk actions, schedules, queues and a queue's wait time and depth metrics
triggerdevApi Call the connected Trigger.dev REST API

Common questions.

Why does an Observer key fail to connect?

The project identity endpoint requires the No restrictions preset. The connection rejects restricted keys even though Polylane’s operations are read-only.

Can one key connect production and staging?

No. The key identifies one environment. Connect production and staging separately with their own environment keys.

Connect it once. Then get back to shipping.

Get started for free