View all systems 
Trigger.devdeveloper tools
10 available actions
What your AI agent can do in Trigger.dev
Trigger.dev is a platform for building, deploying, and managing reliable background tasks and workflows. This page lists every available action. Your agent only receives the actions and permissions required for the role you approve.
Showing all 10 actions.
Common starting points
- 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.
- Execute TRQL QueryRun one read-only Trigger.dev Query Language SELECT statement for custom run analytics and return JSON rows or CSV text.
- 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.
Browse all 10 actions by capability
Open a capability to see every supported action and its description.
Find & reviewLook up and review existing recordsView 7 actions
- 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.
- 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.
Update & manageChange and manage existing recordsView 1 action
- Execute TRQL QueryRun one read-only Trigger.dev Query Language SELECT statement for custom run analytics and return JSON rows or CSV text.
Other actionsSpecialist and administrative actions.View 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.
Connection record
A connection you can control.
- Sign-in
- Customer-managed key
- Setup
- Use a key you create and control. It is stored securely and limited to the work agreed for the role.
- Boundaries
- Only the approved role and actions.
- Off switch
- Revoke the connection from your account.
FAQ
Before you connect Trigger.dev
How does the agent connect to Trigger.dev?
With a key you create and control. It is stored securely, permissions are limited to what the agent needs, and you can revoke it at any time.
What can the agent actually do in Trigger.dev?
The page above lists the 10 actions currently available through the Trigger.dev connection. The role determines which of those actions the agent may use, and write access is only enabled when the workflow needs it.
Is Trigger.dev included in my plan?
Connections are priced per tool on top of the base plan. Some are included and some are premium. See pricing for how connection charges work.
How long until Trigger.dev is ready?
Timing depends on the sign-in method, permissions and workflow being connected. We confirm the scope and setup plan before enabling the connection.
Bring the workflow together
Ready to put Trigger.dev to work?
Start with the responsibility you want off your plate. We’ll map the connection and the boundaries around it.