The Trigger.dev connector for Muse

Background jobs, triggered and tracked by asking.

The Trigger.dev connector lets Muse work with your background jobs: trigger runs on demand, list recent executions, and manage schedules. Long-running tasks stop being invisible — ask what ran, what failed, and what’s scheduled next.

Developers use it for ops without the dashboard: kick off a backfill, check why last night’s job failed, or pause a schedule, all in plain language.

What Muse can do with Trigger.dev

Trigger background jobs on demand
List runs with status, duration, and errors
Manage and pause job schedules
Investigate failed runs and their error output

Try asking

“Trigger the nightly sync job now instead of waiting.”
“Why did the report job fail last night?”
“List all scheduled jobs and pause the weekly cleanup.”

Safety notes

Triggering jobs runs real workloads — Muse confirms which job before firing.
Failed-run output may contain sensitive data; handle it accordingly.
This is a community-built connector. Review its permissions before connecting.

How to connect Trigger.dev

Open the Muse app, go to settings, and find connectors. Link your Trigger.dev account with the standard sign-in — Muse never sees your password. Once linked, the connector is available across your conversations. You can scope it to read-only or disconnect it entirely at any time from the same screen.

Questions

Can Muse create new Trigger.dev jobs?

The connector triggers, lists, and manages existing jobs and schedules. Writing new job code stays in your codebase.

Does it show real-time run progress?

It can poll run status on request. For live streaming logs, use the Trigger.dev dashboard.

Related connectors

Connector status last checked October 13, 2026. The authoritative, current list lives in the Muse app's settings, under connectors. Back to the full directory →