Trigger.dev Tools

The Trigger.dev provider lets a workflow kick off background tasks in Trigger.dev and read back the status and output of their runs. Use these tools when you want to hand off long-running or asynchronous work (emails, ETL jobs, scheduled processing) to Trigger.dev and then poll or list the resulting runs from your Zelaxy workflow.

Overview

All requests authenticate with a Trigger.dev secret key sent as Authorization: Bearer <apiKey>. The key is treated as a secret (user-only visibility, rendered as a password field in the block).

Operations

Configuration

trigger_dev_trigger_task

Triggers a task via POST https://api.trigger.dev/api/v1/tasks/{taskIdentifier}/trigger.

trigger_dev_get_run

Retrieves a single run via GET https://api.trigger.dev/api/v3/runs/{runId}.

trigger_dev_list_runs

Lists runs via GET https://api.trigger.dev/api/v3/runs with optional query filters.

Outputs

trigger_dev_trigger_task

• data (json) — The triggered run object returned by Trigger.dev.
• metadata (json) — Run identifiers.
  • metadata.id (string) — ID of the run that was triggered.

trigger_dev_get_run

• data (json) — The Trigger.dev run object (includes status and output).
• metadata (json) — Run identifiers.
  • metadata.id (string) — Run ID.

trigger_dev_list_runs

• data (json) — Array of Trigger.dev run objects (the data array from the API response).
• metadata (json) — List metadata.
  • metadata.count (number) — Number of runs returned.

YAML Example

trigger_dev_1:
  type: trigger_dev
  name: "Trigger.dev"
  inputs:
    operation: "trigger_dev_trigger_task"
    taskIdentifier: "send-welcome-email"
    payload: '{"userId":"user_123"}'
    idempotencyKey: "welcome-user_123"
    apiKey: "{{TRIGGER_DEV_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

To check on the run later, point a second block at trigger_dev_get_run and reference the triggered run id:

trigger_dev_2:
  type: trigger_dev
  name: "Trigger.dev"
  inputs:
    operation: "trigger_dev_get_run"
    runId: "{{trigger_dev_1.metadata.id}}"
    apiKey: "{{TRIGGER_DEV_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Auth setup: Create a secret key in your Trigger.dev project (tr_...) and store it as an environment variable (e.g. TRIGGER_DEV_API_KEY). Reference it with {{TRIGGER_DEV_API_KEY}}. The key's environment (dev/staging/prod) determines which runs trigger_dev_list_runs returns.
• Trigger then poll: Capture the new run id from {{trigger_dev_1.metadata.id}} after a Trigger task, then feed it into trigger_dev_get_run (or filter trigger_dev_list_runs) to read the run's status and output once it completes.
• Idempotency: Set idempotencyKey on trigger_dev_trigger_task when retrying or running in a loop so the same logical task isn't triggered twice for the same key.
• API versions differ per operation: triggering uses the v1 endpoint while get/list runs use v3 — this is intentional and matches the Trigger.dev API; no extra configuration is needed.