Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Trigger.dev (BYOK) — connector documentation

  • MCP endpoint: https://byok-trigger-dev.connectorbay.com/mcp
  • REST API: POST https://byok-trigger-dev.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-trigger-dev.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Trigger.dev environment secret key (tr_prod_sk_... or tr_dev_sk_...), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-trigger-dev.connectorbay.com/health · Tool schemas: https://byok-trigger-dev.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-trigger-dev · agent@connectorbay.com

What Trigger.dev (BYOK) is for

Trigger.dev (BYOK) lets an AI assistant read your own Trigger.dev data through the Trigger.dev API with a key you supply (environment secret key (tr_prod_sk_... or tr_dev_sk_...)). Read-only: 9 tools (list_runs, get_run, list_schedules, list_deployments, get_latest_deployment, list_queues, list_error_groups, list_concurrency_limits, get_batch). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.trigger.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Trigger.dev. Trigger.dev and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Trigger.dev runs failed in the last day?"
  • "What happened in run run_abc123?"
  • "Which Trigger.dev schedules are active and when do they run next?"
  • "What were the latest Trigger.dev deployments and did they succeed?"
  • "Which version is currently deployed on Trigger.dev?"
  • "Which Trigger.dev queues are backed up?"

What it does

  • list_runs: List task runs of the environment the key belongs to, newest first. Without a time filter only the last 7 days are returned. Returns status, task, version, timing and cost, never payloads or outputs.
  • get_run: Get one run: status, task, version, timing, cost, attempt depth, batch and tags. Payload and output are not returned.
  • list_schedules: List the cron and imperative schedules of the environment with task, generator expression, timezone, active flag and next run.
  • list_deployments: List deployments of the project, newest first, with version, runtime, status and deploy time.
  • get_latest_deployment: Get the most recent deployment: id, version, status and image reference.
  • list_queues: List task queues with running and queued counts, paused state and concurrency limit.
  • list_error_groups: List grouped task errors with task, error type and message, occurrence count and first and last seen times.
  • list_concurrency_limits: List named concurrency limits with current and base values, running and queued counts and paused state.
  • get_batch: Get a batch of runs: status, run count, successful and failed counts and creation time. Per-run errors are not returned.

BYOK key

You bring your own Trigger.dev environment secret key (tr_prod_sk_... or tr_dev_sk_...) (https://cloud.trigger.dev). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.trigger.dev over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Trigger.dev API (api.trigger.dev) with a BYOK key; documentation: https://trigger.dev/docs/management/overview. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Trigger.dev. Trigger.dev and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Trigger.dev account.

Built for: Worldwide. Languages: English.