Trigger.dev
Trigger.dev is a platform for building, deploying, and managing reliable background tasks and workflows.
Integration
- Vendor
- Trigger.dev
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 10
- Composio slug
trigger_dev
Tools
- Batch Trigger Task
Start multiple runs of one deployed Trigger.dev task in one provider-side batch and return the batch and run IDs.
- Execute TRQL Query
Run one read-only Trigger.dev Query Language SELECT statement for custom run analytics and return JSON rows or CSV text.
- Get Batch
Retrieve a task batch's status, run IDs, completion counts, and item errors.
- Get Batch Results
Retrieve the success or failure outcome and encoded output for every run in a completed task batch.
- Get Error
Retrieve one Trigger.dev error group's message, occurrence history, affected versions, and resolution or ignore state.
- Get Run
Retrieve 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 Result
Retrieve one run's compact success or failure result, including its encoded output or error and usage duration.
- List Errors
Return one forward page of Trigger.dev error groups, optionally filtered by task, version, status, text, or time window.
- List Runs
Return one forward page of runs in the connected environment, optionally filtered by time, status, task, version, tags, schedule, bulk action, test mode, or error.
- Trigger Task
Start one run of a deployed Trigger.dev task and return the new run ID.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Trigger.dev.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Trigger.dev tools in chat.
What teammates see: by default, memories from Trigger.dev are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.