Get started with Trigger.dev in your favorite framework.

Introduction

Trigger.dev

How to get started in 3 minutes using the CLI and SDK.

Quick start

How it works

Beta upgrade

Upgrade to new build system

There are some hard and soft limits in v3 that you might hit.

Limits

Triggering

Apikeys

This file is used to configure your project and how it's built.

Configuration

The trigger.config.ts file

The `trigger.dev dev` command is used to run your tasks locally.

CLI dev command

Run tests

Deploy environment variables

The `trigger.dev deploy` command can be used to manually deploy.

CLI deploy command

You can easily deploy your tasks with GitHub actions.

GitHub Actions

Writing tasks introduction

Logging

How to deal with errors and write reliable tasks.

Errors & Retrying

Queue concurrency

Versioning

Machines

Idempotency

Replaying

Notifications

Run usage

Overview

The Trigger.dev CLI has a number of options and commands to help you develop locally, self host, and deploy your tasks.

You can self-host Trigger.dev on your own infrastructure.

Self-hosting

Open source contributing

Github repo

Changelog

Roadmap

Some common problems you might experience and their solutions

Common problems

Upgrading packages

Troubleshooting alerts

Troubleshooting uptime status

Troubleshooting github issues

Request feature

Community

Help slack

Help email

This guide will show you how to setup Trigger.dev with Bun

Bun guide

This guide will show you how to setup Trigger.dev in your existing Next.js project, test an example task, and view the run.

Next.js

Next.js setup guide

This guide will show you how to setup Trigger.dev in your existing Node.js project, test an example task, and view the run.

Node.js

Node.js setup guide

This guide will show you how to setup Trigger.dev in your existing Remix project, test an example task, and view the run.

Remix

Remix setup guide

Creating a project

Upgrading from v2

Intro

Dall e3 generate image

Ffmpeg video processing

Open ai with retrying

Sharp image processing

React pdf

Resend email sequence

Vercel ai sdk

Guides

Examples

Switch to v2 docs

Discord

When you deploy to Vercel, automatically deploy your associated tasks.

Vercel integration

During your run you can wait for a period of time or for something to happen.

Wait: Overview

Wait for a period of time, then continue execution.

Wait for

Wait until a date, then continue execution.

Wait until

Wait until an event has been received, then continue execution.

Wait for event

Wait until a `Request` has been received at the provided URL, then continue execution.

Wait for request

Use these options when logging in to Trigger.dev using the CLI.

login

CLI login command

Use these options when running the CLI `init` command.

init

CLI init command

Use these options to help deploy your tasks to Trigger.dev.

deploy

CLI deploy options

Use these options to display the current logged in user and project details.

whoami

CLI whoami command

Use these options when using the `logout` CLI command.

logout

CLI logout command

Use these options when using the `list-profiles` CLI command.

list-profiles

CLI list-profiles command

Use these options when using the `update` CLI command.

update

CLI update command

This guide will show you how to trigger a task from a Supabase edge function, and then view the run in our dashboard.

Edge function hello world

Triggering tasks from Supabase edge functions

This guide will show you how to trigger a task when a row is added to a table using Supabase database webhooks.

Frameworks

Dashboard

Migrations

Introduction