---
title: "Trigger.dev integration for LuumenAI"
url: "https://www.luumen.ai/integrations/trigger-dev/"
entity: SoftwareIntegration
category: "Source control & CI/CD"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Trigger.dev integration for LuumenAI

Read run history and errors, then retrigger the tasks that failed.

## What LuumenAI can do with Trigger.dev

LuumenAI connects to Trigger.dev with an API token and exposes 10 tools (8 read-only · 2 write). For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

## Key facts

- Authentication: API token
- Tools available: 10 tools (8 read-only · 2 write)
- Deployment: scoped as part of your Pilot, Platform, or Managed rollout
- Category: Source control & CI/CD

## About Trigger.dev with LuumenAI

Connect Trigger.dev and Luumen can read your background tasks the way you would: list runs in the connected environment, open a single run's payload, output, attempts, and cost, and pull the error records behind a failure. When a task needs to run again, Luumen prepares the trigger with its payload and holds it for your approval. Authentication is by API key.

## Example tools

Read-only (8 in total):

- `TRIGGER_DEV_EXECUTE_TRQL_QUERY` — Run one read-only Trigger.dev Query Language SELECT statement for custom run analytics and return JSON rows or CSV text.
- `TRIGGER_DEV_GET_BATCH` — Retrieve a task batch's status, run IDs, completion counts, and item errors.
- `TRIGGER_DEV_GET_BATCH_RESULTS` — Retrieve the success or failure outcome and encoded output for every run in a completed task batch.
- `TRIGGER_DEV_GET_ERROR` — Retrieve one Trigger.dev error group's message, occurrence history, affected versions, and resolution or ignore state.
- `TRIGGER_DEV_GET_RUN` — Retrieve one run's status, timing, payload, output, attempts, metadata, relationships, schedule, and cost details.
- `TRIGGER_DEV_GET_RUN_RESULT` — Retrieve one run's compact success or failure result, including its encoded output or error and usage duration.
- `TRIGGER_DEV_LIST_ERRORS` — Return one forward page of Trigger.dev error groups, optionally filtered by task, version, status, text, or time window.
- `TRIGGER_DEV_LIST_RUNS` — Return one forward page of runs in the connected environment, optionally filtered by time, status, task, version, tags, schedule, bulk action, test mode, or error.

Write and destructive (2 in total, subject to configured approval policy):

- `TRIGGER_DEV_BATCH_TRIGGER_TASK` — Start multiple runs of one deployed Trigger.dev task in one provider-side batch and return the batch and run IDs.
- `TRIGGER_DEV_TRIGGER_TASK` — Start one run of a deployed Trigger.dev task and return the new run ID.

## Frequently asked questions

### How does LuumenAI connect to Trigger.dev?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Trigger.dev on its own?

For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

### Is there an audit trail?

Every call to Trigger.dev — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/trigger-dev/