Trigger.dev integration
Trigger.dev runs background jobs and long-running tasks for an application. Trigger a task run and read, replay, reschedule, cancel or list runs and their traces, submit and read batches, run bulk actions, manage schedules and environment variables, read queues and worker deployments, upload and read run payloads and outputs, and manage waitpoint tokens for human-in-the-loop pauses. Authentication is a project secret key sent as a bearer token, and that key also selects the environment.
Say what should happen.
The workflow builds itself.
What you can do with Trigger.dev
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Envvar, 5 operations
create_project_envvar_v1Create project envvar v1POSTCreate environment variable.delete_envvarDelete envvarDELETEDelete environment variable.get_envvarGet envvarGETRetrieve environment variable.list_project_envvars_v1List project envvars v1GETList environment variables.update_project_envvar_v1Update project envvar v1PUTUpdate environment variable.
Schedule, 5 operations
create_schedule_v1Create schedule v1POSTCreate a schedule.delete_scheduleDelete scheduleDELETEDelete Schedule.get_scheduleGet scheduleGETRetrieve Schedule.list_schedules_v1List schedules v1GETList all schedules.update_schedule_v1Update schedule v1PUTUpdate Schedule.
Session, 4 operations
create_session_v1Create session v1POSTCreate a session.list_sessions_v1List sessions v1GETList sessions.retrieve_session_v1Retrieve session v1GETRetrieve a session.update_session_v1Update session v1PATCHUpdate a session.
Bulk action, 3 operations
create_bulk_action_v1Create bulk action v1POSTCreate bulk action.list_bulk_actions_v1List bulk actions v1GETList bulk actions.retrieve_bulk_action_v1Retrieve bulk action v1GETRetrieve bulk action.
Run, 3 operations
list_project_runs_v1List project runs v1GETList project runs.list_runs_v1List runs v1GETList runs.retrieve_run_v1Retrieve run v1GETRetrieve a run.
Token, 3 operations
create_waitpoint_token_v1Create waitpoint token v1POSTCreate a waitpoint token.list_waitpoint_tokens_v1List waitpoint tokens v1GETList waitpoint tokens.retrieve_waitpoint_token_v1Retrieve waitpoint token v1GETRetrieve a waitpoint token.
Batch, 2 operations
batch_trigger_task_by_id_v1Batch trigger task by id v1POSTBatch trigger a specific task.batch_trigger_task_v1Batch trigger task v1POSTBatch trigger tasks.
Deployment, 2 operations
get_deploymentGet deploymentGETGet deployment.list_deployments_v1List deployments v1GETList deployments.
Error, 2 operations
list_errors_v1List errors v1GETList errors.retrieve_error_v1Retrieve error v1GETRetrieve an error.
Queue, 2 operations
list_queues_v1List queues v1GETList all queues.retrieve_queue_v1Retrieve queue v1GETRetrieve a queue.
Result, 2 operations
list_resultList resultGETRetrieve run result.list_resultsList resultsGETRetrieve batch results.
Abort, 1 operation
abort_bulk_action_v1Abort bulk action v1POSTAbort bulk action.
Activate, 1 operation
activate_schedule_v1Activate schedule v1POSTActivate Schedule.
Batche, 1 operation
retrieve_batch_v1Retrieve batch v1GETRetrieve a batch.
Callback, 1 operation
update_callbackUpdate callbackPOSTComplete a waitpoint token via HTTP callback.
Cancel, 1 operation
cancel_run_v1Cancel run v1POSTCancel a run.
Close, 1 operation
close_session_v1Close session v1POSTClose a session.
Complete, 1 operation
complete_waitpoint_token_v1Complete waitpoint token v1POSTComplete a waitpoint token.
Dashboard, 1 operation
list_dashboards_v1List dashboards v1GETList built-in dashboards.
Deactivate, 1 operation
deactivate_schedule_v1Deactivate schedule v1POSTDeactivate Schedule.
Event, 1 operation
list_eventsList eventsGETRetrieve run events.
Ignore, 1 operation
ignore_error_v1Ignore error v1POSTIgnore an error.
Import, 1 operation
upload_project_envvars_v1Upload project envvars v1POSTUpload environment variables.
Latest, 1 operation
list_latestList latestGETGet latest deployment.
Metadata, 1 operation
update_run_metadata_v1Update run metadata v1PUTUpdate run metadata.
Override, 1 operation
override_queue_concurrency_v1Override queue concurrency v1POSTOverride queue concurrency limit.
Pause, 1 operation
pause_queue_v1Pause queue v1POSTPause or resume a queue.
Promote, 1 operation
promote_deployment_v1Promote deployment v1POSTPromote deployment.
Query, 1 operation
execute_query_v1Execute query v1POSTExecute a TRQL query.
Replay, 1 operation
replay_run_v1Replay run v1POSTReplay a run.
Reschedule, 1 operation
reschedule_run_v1Reschedule run v1POSTRescheduled a delayed run.
Reset, 1 operation
reset_queue_concurrency_v1Reset queue concurrency v1POSTReset queue concurrency limit.
Resolve, 1 operation
resolve_error_v1Resolve error v1POSTResolve an error.
Schema, 1 operation
list_schemaList schemaGETGet query schema.
Tag, 1 operation
add_run_tags_v1Add run tags v1POSTAdd tags to a run.
Timezone, 1 operation
list_timezonesList timezonesGETGet all supported timezones.
Trace, 1 operation
list_traceList traceGETRetrieve run trace.
Trigger, 1 operation
trigger_task_v1Trigger task v1POSTTrigger a task.
Unresolve, 1 operation
unresolve_error_v1Unresolve error v1POSTUnresolve an error.
Use Trigger.dev from Claude Code, Cursor or Codex
Connect Trigger.dev in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Trigger.dev operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Trigger.dev
- Create your workspace
Sign up free. Nothing to install.
- Connect Trigger.dev once
Add your Trigger.dev connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Trigger.dev integration FAQ
What can you do with the Trigger.dev integration?
LiveContext exposes 61 operations on Trigger.dev, covering envvar, schedule, session and bulk action.
