All integrationsCloud Computing

Trigger.dev

Run and manage your Trigger.dev background tasks: trigger a task or a batch of runs, find, replay, cancel and tag runs, manage schedules, environment variables and queues, and start a workflow when a run starts, completes, fails or changes status.

actions
26
triggers
4

Triggers

Start a workflow when something happens in Trigger.dev.

  • New runRuns when a task run is triggered in Trigger.dev, in the API key's environment, after this watch starts.
  • Run completedRuns when a task run finishes successfully in Trigger.dev after this watch starts, with the run's output.
  • Run failedRuns when a task run fails, crashes or times out in Trigger.dev after this watch starts, with the run's error.
  • Run status changedRuns each time a task run moves to a new status in Trigger.dev, such as Running or Completed, after this watch starts.

Actions

Steps a workflow can run in Trigger.dev.

  • Trigger taskStart a run of one of your tasks with a payload, now or at a set time, in the environment the API key belongs to. Returns the run's id; the 'Run completed' trigger says when it finishes.
  • Trigger task for each itemStart one run of a task for each payload in a list (up to 1,000), in one request. Returns the batch's id and the id of every run.
  • List runsList runs, newest first, filtered by status, task, when they were created, tag, schedule or version. Without a period or dates, only the last 7 days. Returns one page; pass 'next_cursor' for more.
  • Get runGet one run with its status, payload, output or error, each attempt, and the runs it is linked to.
  • Replay runStart a new run of the same task with the same payload and options as an earlier run, optionally with a different payload, start time or tags. Returns the new run's id.
  • Cancel runCancel a run that is waiting or running. A run that has already finished is left as it is.
  • Change delayed run's start timeMove the start time of a run that is waiting for one (status DELAYED), such as one triggered with a start time.
  • Add tags to runAdd tags to a run, to find it by later. A run holds at most 10; tags it already has are ignored.
  • Set run metadataReplace a run's metadata (its own keys and values, which the task can read and show in the dashboard) with the keys and values given.
  • Get batchGet a batch of runs: its status, the ids of its runs, and how many started or failed to start.
  • List schedulesList the environment's schedules with their task, cron, time zone, whether each is on and when it next runs.
  • Create scheduleRun a scheduled task on a cron schedule, in a time zone of your choice. Creating the same schedule again changes it rather than making a copy.
  • Get scheduleGet one schedule with its task, cron, time zone, whether it is on and when it next runs.
  • Update scheduleChange a schedule's task, cron, time zone or your own ID. Only what is given changes. Schedules written in code can only change in code.
  • Turn schedule on or offTurn a schedule on (active) or off (inactive). An inactive schedule keeps its settings but starts no runs.
  • Delete scheduleDelete a schedule made in the dashboard or with 'Create schedule'. Schedules written in code can only be removed in code.
  • List environment variablesList the environment variables your tasks get in the API key's environment. Secret variables' values come back hidden.
  • Get environment variableGet one environment variable's value.
  • Create environment variableAdd an environment variable for your tasks. One of the same name is overwritten. Tasks get it from their next run.
  • Update environment variableChange the value of an environment variable that already exists.
  • Delete environment variableDelete an environment variable from the API key's environment.
  • Import environment variablesAdd several environment variables at once from names and values, optionally replacing ones that already exist.
  • List queuesList the environment's queues with how many runs each has waiting and running, its limit, and whether it is paused.
  • Get queueGet one queue with how many runs it has waiting and running, its limit, and whether it is paused.
  • Pause or resume queuePause a queue, so no new runs start from it (runs already going finish), or set it running again.
  • List deploymentsList the environment's deployments, newest first, with their version and status, optionally only those in one status or time range.

Automate Trigger.dev with Lodol.

Connect Trigger.dev and ask your AI for your first workflow.

Free plan, no credit card