Set up Trigger.dev in your project. Use when adding Trigger.dev for the first time, creating trigger.config.ts, or initializing the trigger directory.
Trigger.dev Setup
Get Trigger.dev running in your project in minutes.
When to Use
- Adding Trigger.dev to an existing project
- Creating your first task
- Setting up trigger.config.ts
- Connecting to Trigger.dev cloud
Prerequisites
- Node.js 18+ or Bun
- A Trigger.dev account (https://cloud.trigger.dev)
Quick Start
1. Install the SDK
npm install @trigger.dev/sdk
2. Initialize Your Project
npx trigger init
This creates:
trigger.config.ts- project configurationtrigger/directory - where your tasks livetrigger/example.ts- a sample task
3. Configure trigger.config.ts
import { defineConfig } from "@trigger.dev/sdk";
export default defineConfig({
project: "proj_xxxxx", // From dashboard
dirs: ["./trigger"],
});
4. Create Your First Task
// trigger/my-task.ts
import { task } from "@trigger.dev/sdk";
export const myFirstTask = task({
id: "my-first-task",
run: async (payload: { name: string }) => {
console.log(`Hello, ${payload.name}!`);
return { message: `Processed ${payload.name}` };
},
});
5. Start Development Server
npx trigger dev
6. Trigger Your Task
From your app code:
import { tasks } from "@trigger.dev/sdk";
import type { myFirstTask } from "./trigger/my-task";
await tasks.trigger<typeof myFirstTask>("my-first-task", {
name: "World",
});
Or from the Trigger.dev dashboard "Test" tab.
Project Structure
your-project/
├── trigger.config.ts # Required - project config
├── trigger/ # Required - task files
│ ├── my-task.ts
│ └── another-task.ts
├── package.json
└── ...
Environment Variables
Create .env or set in your environment:
TRIGGER_SECRET_KEY=tr_dev_xxxxx # From dashboard > API Keys
Common Issues
"No tasks found"
- Ensure tasks are exported from files in
dirsfolders - Check
trigger.config.tspoints to correct directories
"Project not found"
- Verify
projectin config matches dashboard - Check
TRIGGER_SECRET_KEYis set
"Task not registered"
- Restart
npx trigger devafter adding new tasks - Tasks must use
task()orschemaTask()from@trigger.dev/sdk
Next Steps
- Add retry logic → see trigger-tasks skill
- Configure build extensions → see trigger-config skill
- Build AI workflows → see trigger-agents skill
- Add real-time UI → see trigger-realtime skill
You Might Also Like
Related Skills

verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
facebook
test
Use when you need to run tests for React core. Supports source, www, stable, and experimental channels.
facebook
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
facebook
extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.
facebook