Trigger Setup

Getting started with Trigger.dev

Set up Trigger.dev in an existing project. The end state is: the SDK installed, a trigger.config.ts pointing at a project ref, a /trigger directory with at least one exported task, and trigger dev running so the task shows up in the dashboard.

The fastest path is the CLI’s own wizard, which performs every mechanical step below and also offers to install the MCP server and these agent skills:

npx trigger.dev@latest init

Prefer init when you can. Do the manual steps further down when init does not fit (monorepos, an existing config to extend, or a non-interactive environment).

Authentication needs the human

The CLI can start account creation, but a person must verify their email and authorize access. In an agent session, start a resumable login instead of blocking on the CLI:

npx trigger.dev@latest login --email user@example.com --name "Alex Smith" --no-browser --no-wait

Give the printed URL to the user and ask them to complete sign-in and authorization. After they confirm, resume the saved authorization:

npx trigger.dev@latest login --no-browser

Do not create accounts or approve CLI access on the user’s behalf. Once authenticated, trigger init can create the first organization and project without a dashboard handoff. A self-hosted instance may disable organization creation; if it does, ask the user to create the organization in its dashboard first.

Manual setup

1. Authenticate (human authorization step)

For an interactive terminal:

npx trigger.dev@latest login

For an agent or headless terminal, use the resumable flow described above. Add --api-url https://your-trigger-instance.com to both commands for self-hosting.

2. Install the packages

@trigger.dev/sdk is a runtime dependency; @trigger.dev/build is a dev dependency. Pin both to the same version as the trigger.dev CLI you run; the CLI warns on a mismatch during dev/deploy.

npm add @trigger.dev/sdk@latest
npm add --save-dev @trigger.dev/build@latest

3. Write trigger.config.ts

Create it in the project root (or trigger.config.mjs for JavaScript). The project ref and dirs are the only required fields.

import { defineConfig } from "@trigger.dev/sdk";

export default defineConfig({
  project: "<project ref>", // e.g. "proj_abc123", from the dashboard
  dirs: ["./src/trigger"], // where your tasks live
  maxDuration: 3600,
  retries: {
    enabledInDev: false,
    default: { maxAttempts: 3, factor: 2, minTimeoutInMs: 1000, maxTimeoutInMs: 10000, randomize: true },
  },
});

Use the Bun runtime by adding runtime: "bun". Build extensions (prismaExtension, puppeteer, additionalFiles, etc.) come from @trigger.dev/build and go in build.extensions.

4. Add a first task

Create the directory that matches dirs and export a task from it. Every task must be a named export with a project-unique id.

// src/trigger/example.ts
import { task } from "@trigger.dev/sdk";

export const helloWorld = task({
  id: "hello-world",
  run: async (payload: { name: string }) => {
    return { message: `Hello ${payload.name}!` };
  },
});

5. Wire tsconfig and gitignore

Add trigger.config.ts to the include array in tsconfig.json, and add .trigger to .gitignore (the CLI writes local dev state there).

// tsconfig.json
{ "include": ["trigger.config.ts" /* ...existing */] }

# .gitignore
.trigger

6. Create an environment API key (human step)

For triggering from your own code, create a named API key with Trigger only access in your Development environment and set it as TRIGGER_SECRET_KEY. Self-hosted users also set TRIGGER_API_URL.

# .env (or .env.local for Next.js)
TRIGGER_SECRET_KEY=tr_dev_sk_xxxxxxxx

7. Run the dev server

npx trigger.dev@latest dev

Leave it running. Tasks register with the dashboard, where the user can fire a test run from the task’s test page. On first run the CLI offers to install the MCP server and agent skills; recommend both.

Triggering from your app

Once a task exists, trigger it from backend code with a type-only import so the task code is never bundled into your app. Trigger by id, not by calling the task object.

import { tasks } from "@trigger.dev/sdk";
import type { helloWorld } from "@/trigger/example"; // type-only

const handle = await tasks.trigger<typeof helloWorld>("hello-world", { name: "Ada" });

TRIGGER_SECRET_KEY must be set wherever this runs. Framework specifics live in the Next.js / Remix / Node.js guides.

Monorepos

Two layouts, both supported: put tasks in a shared package (@repo/tasks with its own trigger.config.ts, consumed via workspace:*), or install Trigger.dev directly in the app that needs it. Run trigger dev from the directory that holds trigger.config.ts. See the manual setup docs for full Turborepo examples before scaffolding either.

Common mistakes

1. Blocking an agent session on login. Email verification and authorization require the user, but the CLI authorization itself is resumable.

   • Wrong: spawning trigger login and polling indefinitely in an agent session.
   • Correct: run trigger login --email <email> --name <full-name> --no-browser --no-wait, give the URL to the user, then resume with trigger login --no-browser after they approve.

2. Mismatched CLI and SDK versions. A trigger.dev CLI on a different major than @trigger.dev/sdk breaks dev/deploy.

   • Wrong: npx trigger.dev@latest dev against an old pinned SDK.
   • Correct: keep trigger.dev, @trigger.dev/sdk, and @trigger.dev/build on the same version.

3. Importing from @trigger.dev/sdk/v3 or using client.defineJob(). Both are old.

   • Correct: always import from @trigger.dev/sdk; define work with task().

4. Tasks not exported, or outside dirs. A task that is not a named export inside a configured directory will not be picked up.

   • Correct: export const ... = task({ ... }) in a file under a dirs path.

5. Importing the task instance into backend code. This bundles the task.

   • Wrong: import { helloWorld } from "@/trigger/example" in a route handler.
   • Correct: import type { helloWorld } plus tasks.trigger<typeof helloWorld>("hello-world", payload).

6. Forgetting TRIGGER_SECRET_KEY. Triggering from your app fails without it; the dev server itself works once the CLI is logged in.

References

Sibling skills:

• trigger-tasks for writing the tasks themselves once setup is done: retries, waits, queues, scheduled tasks, triggering, and the full trigger.config.ts.
• trigger-realtime for showing live run status in a frontend.
• trigger-authoring-chat-agent and trigger-chat-agent-advanced for building AI chat agents.

Docs:

• Quick start (opens in a new tab)
• Manual setup (opens in a new tab)
• Configuration file (opens in a new tab)

Version

Generated for @trigger.dev/sdk 4.8.3. Re-run the trigger.dev skills installer after upgrading.