baseboard
All integrations

Jobs & syncs

Trigger.dev

See failed runs and replay them.

What you see

  • Background jobs

    On the Jobs page as soon as Trigger.dev is connected.

How to connect

  • Paste a key

    The environment's tr_prod_… (or tr_dev_…) secret key, from the project's API keys page. Tag runs with the user's email to see them per customer. Get a key The key is checked against Trigger.dev before it’s saved, then sealed so only the broker that calls Trigger.dev can open it.
  • From a terminal

    The CLI asks for the same key at a hidden prompt, so an agent running it never sees the key.
    $ npx baseboard-cli connect trigger --project k57abc

Settings

Hostoptional
For example https://api.trigger.dev

Connect Trigger.dev and the rest of your stack in one place.

Free covers one project with three connections. Everyone starts read-only.