Skip to content

docs: document the TRIGGER_DASHBOARD_URL run environment variable #5049

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ericallam merged 1 commit into from
Oct 22, 2026
Merged

docs: document the TRIGGER_DASHBOARD_URL run environment variable #5049

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/deploy-environment-variables.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,6 +192,25 @@ The context object provides:

For more information about the context object, see the [Context documentation](/context).

#### Linking to a run in the dashboard

Trigger.dev sets `TRIGGER_DASHBOARD_URL` on every run, in development and deployed environments. Its value is the dashboard's address without a trailing slash, so it also points at your own instance when you self-host. Append `/runs/<runId>` to link to a run:
Comment thread
ericallam marked this conversation as resolved.

```ts
Comment thread
ericallam marked this conversation as resolved.
import { task } from "@trigger.dev/sdk";

export const reportTask = task({
id: "report-task",
run: async (payload, { ctx }) => {
const runUrl = `${process.env.TRIGGER_DASHBOARD_URL}/runs/${ctx.run.id}`;

console.log(`View this run: ${runUrl}`);
},
});
```

The `/runs/<runId>` link checks that the viewer is a member of the run's organization, then redirects to the full run page. If you set your own `TRIGGER_DASHBOARD_URL` environment variable on the project, your value is used instead.

### Sync env vars from another service

There are two ways to pull secrets from another service into Trigger.dev: a native **Secret Sync** (currently [Infisical](https://infisical.com)), or the `syncEnvVars` build extension for any other service.
Expand Down
Loading