Trigger.dev for AI agents
Agents read Trigger.dev at once. Changes and sends are held for a person's approval by default.
About Trigger.dev
Trigger.dev is a platform for building, deploying, and managing reliable background tasks and workflows.
What an agent can do in Trigger.dev
Every Trigger.dev action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Trigger.dev without asking first. 8 actions.
- Execute TRQL QueryRun one read-only Trigger.dev Query Language SELECT statement for custom run analytics and return JSON rows or CSV text.
- Get BatchRetrieve a task batch's status, run IDs, completion counts, and item errors.
- Get Batch ResultsRetrieve the success or failure outcome and encoded output for every run in a completed task batch.
- Get ErrorRetrieve one Trigger.dev error group's message, occurrence history, affected versions, and resolution or ignore state.
- Get RunRetrieve one run's status, timing, payload, output, attempts, metadata, relationships, schedule, and cost details. Presigned payload or output URLs are returned without fetching their content.
- Get Run ResultRetrieve one run's compact success or failure result, including its encoded output or error and usage duration.
- List ErrorsReturn one forward page of Trigger.dev error groups, optionally filtered by task, version, status, text, or time window.
- List RunsReturn one forward page of runs in the connected environment, optionally filtered by time, status, task, version, tags, schedule, bulk action, test mode, or error.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 2 actions.
- Batch Trigger TaskStart multiple runs of one deployed Trigger.dev task in one provider-side batch and return the batch and run IDs.
- Trigger TaskStart one run of a deployed Trigger.dev task and return the new run ID.
Changes wait in Needs you
Changes and sends in Trigger.dev are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
Trigger.dev questions
Can an agent change data in Trigger.dev on its own?
Not by default. Changes and sends in Trigger.dev are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Trigger.dev?
This connector lists 8 read actions. Reads run at once, without waiting for approval.
How does Trigger.dev connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.