Trigger.dev
Trigger.dev · Developer tools
Background jobs and AI workflows: tasks and runs
The client pastes their secret key from Trigger.dev's settings. We store it encrypted.
Tested against Trigger.dev's live API.
Building with Trigger.dev? The docs have setup steps and code for every tool.
Open the Trigger.dev docsTools
Your agent calls any endpoint of Trigger.dev's API with the request tool, with the client's access attached.
Base URL for request
https://api.trigger.dev/api/v1
request
HTTPS ANY /v1/clients/{clientId}/trigger-dev/{path}
Any endpoint of Trigger.dev's own API, with the client's access attached.
- servicestringrequired
- This service: trigger-dev
- methodstringrequired
- GET, POST, PUT, PATCH or DELETE
- pathstringrequired
- The path under https://api.trigger.dev/api/v1
- queryobjectoptional
- Query parameters
- bodyobjectoptional
- A JSON body
Over MCP every tool also takes client_id, from list_clients. Over HTTPS send it as clientId to https://api.operate.as/v1.
What the client approves
- Use the Trigger.dev key you paste, with only the access you gave that key
Get started
Send your next client one link
Add a client, select the services, copy the link. You'll get an email the moment their access is ready. Start free, no card required. Paid plans are one flat monthly price, and a busy month never takes your agents offline.