Trigger.dev

#What Antimetal does with Trigger.dev

• Monitor background job and task run status
• Find failed or stalled runs in the window around an incident
• Read run logs and errors to understand why a job failed
• Connect a missed job to the downstream symptom it produced

#Connecting Trigger.dev

1. Open Integrations in the Antimetal dashboard

   Go to Integrations and find Trigger.dev.

2. Authorize Antimetal in Trigger.dev

   Click Connect and provide a read-only API key generated in your Trigger.dev project.

3. Confirm the connection

   Once Trigger.dev shows as connected, Antimetal begins pulling task run data into investigations.

#Permissions and access

Antimetal connects with read-only access and performs no write operations — no runs are triggered, cancelled, or modified.

All tenant data is processed in isolated environments. See security and compliance for details.