Connect Trigger.dev to Your AI Agent

Ask your AI assistant to work with Trigger.dev: trigger tasks and follow run results.

6 tools API key

Try a Trigger.dev Task

Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.

oo Skill Trigger.dev

Trigger and Follow a Task

Submit a known task and retrieve its completed result.

/oo Trigger.dev: Trigger task [task identifier] with payload [JSON], follow the returned run ID until completion, then get its execution result.

Review Recent Runs

List runs and inspect selected run details.

/oo Trigger.dev: List Trigger.dev runs matching [task/status/time filters], inspect [run ID], and summarize the returned status and timing.

Start Working with Trigger.dev

  1. Install OOMOL

    Set up oo CLI and the oo Skill in your agent.

    Install OOMOL →
  2. Connect Trigger.dev

    Connect using your Trigger.dev Secret API Key.

    Connect Trigger.dev →
  3. Give Your Agent a Task

    Use /oo with the pages to read, the changes to make, and where to save the result.

    Connection Guide →

Choose Your Agent

  • An account with access to the Trigger.dev resources used in your task.

Trigger.dev Tools

Trigger.dev connects background task submission, run status, and completed execution results to AI workflows.

Trigger and Follow a Task

Submit a known task and retrieve its completed result.

Review Recent Runs

List runs and inspect selected run details.

6 tools

List Runs

List Trigger.dev runs with optional status, task, version, and time filters.

trigger_dev.list_runs

Get Run

Retrieve a Trigger.dev run by ID.

trigger_dev.get_run

Get Run Result

Retrieve the execution result for a completed Trigger.dev run.

trigger_dev.get_run_result

Trigger Task

Trigger a Trigger.dev task by task identifier.

trigger_dev.trigger_task

Cancel Run

Cancel an in-progress Trigger.dev run.

trigger_dev.cancel_run

Replay Run

Replay a Trigger.dev run with the same payload and options.

trigger_dev.replay_run

Frequently Asked Questions

Is triggering the same as completion?

Triggering starts a run; inspect status and request the result after it completes.

Does replay create another run?

Replay runs the same payload and options again.

Can I cancel an in-progress run?

Use the cancel action with its run ID.

Connect Trigger.dev

About Trigger.dev ↗