Trigger.dev

https://trigger.dev/docs
Admin
Trigger.dev is an open source background jobs framework for writing reliable workflows in plain...
Tokens:1,577,286
Snippets:11,145
Trust Score:9.9
Update:2 weeks ago
Show doc for...
Tokens:
Raw
### Example response for listing deployments

Source: https://trigger.dev/docs/management/deployments/list

Example response for a successful GET request to the deployments endpoint. Shows the structure of the data and pagination objects.

```json
{
  "data": [
    {
      "id": "<string>",
      "createdAt": "2023-11-07T05:31:56Z",
      "shortCode": "<string>",
      "version": "<string>",
      "runtime": "<string>",
      "runtimeVersion": "<string>",
      "status": "PENDING",
      "deployedAt": "2023-11-07T05:31:56Z",
      "git": {},
      "error": {},
      "externalId": "<string>"
    }
  ],
  "pagination": {
    "next": "<string>"
  }
}
```

--------------------------------

### Example 5: src/db.ts (modern mode)

Source: https://trigger.dev/docs/llms-full.txt

Database client setup for modern mode using PrismaPg adapter.

```ts
import { PrismaClient } from "./generated/prisma/client.js";
import { PrismaPg } from "@prisma/adapter-pg";

const adapter = new PrismaPg({
  connectionString: process.env.DATABASE_URL!,
});

export const db = new PrismaClient({ adapter });
```

--------------------------------

### GET latest deployment with Go

Source: https://trigger.dev/docs/management/deployments/get-latest

Use this Go example to fetch the latest deployment. Replace <token> with a valid named environment API key. It prints the response body.

```go
package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.trigger.dev/api/v1/deployments/latest"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}
```

--------------------------------

### Go example for retrieving run events

Source: https://trigger.dev/docs/management/runs/retrieve-events

Uses the net/http package to send a GET request with a Bearer token. Prints the response body.

```Go
package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.trigger.dev/api/v1/runs/{runId}/events"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}
```

--------------------------------

### Example 3: src/db.ts (legacy mode)

Source: https://trigger.dev/docs/llms-full.txt

Database client setup for legacy mode, using PrismaClient with a datasource URL from environment variables.

```ts
import { PrismaClient } from "@prisma/client";
export * as sql from "@prisma/client/sql";

export const db = new PrismaClient({
  datasources: {
    db: {
      url: process.env.DATABASE_URL,
    },
  },
});
```

--------------------------------

### Example 1: Standard Prisma 6 setup (legacy mode)

Source: https://trigger.dev/docs/config/extensions/prismaExtension

Standard Prisma 6 setup using legacy mode. The schema.prisma enables typedSql preview feature and uses directUrl for unpooled connections. The trigger.config.ts configures prismaExtension with mode 'legacy', schema path, migrate and typedSql flags, and directUrlEnvVarName.

```prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["typedSql"]
}

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DATABASE_URL_UNPOOLED")
}

```

```typescript
import { defineConfig } from "@trigger.dev/sdk";
import { prismaExtension } from "@trigger.dev/build/extensions/prisma";

export default defineConfig({
  project: process.env.TRIGGER_PROJECT_REF!,
  build: {
    extensions: [
      prismaExtension({
        mode: "legacy",
        schema: "prisma/schema.prisma",
        migrate: true,
        typedSql: true,
        directUrlEnvVarName: "DATABASE_URL_UNPOOLED",
      }),
    ],
  },
});

```

--------------------------------

### List deployments with Go

Source: https://trigger.dev/docs/management/deployments/list

Use this Go example to list deployments using the net/http package. Replace <token> with your API key.

```go
package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.trigger.dev/api/v1/deployments"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}
```

--------------------------------

### GET /api/v1/runs

Source: https://trigger.dev/docs/management/runs/list

This snippet documents the GET /api/v1/runs endpoint, including its query parameters, authorization, request example, response schema, and error handling.

```APIDOC
## GET /api/v1/runs

### Description
List runs from your Trigger.dev project. This endpoint returns a paginated list of runs, with optional filtering and pagination parameters.

### Method
GET

### Endpoint
/api/v1/runs

### Parameters
#### Query Parameters
- **page** (object) - Optional - Use this parameter to paginate the results. You can specify the number of runs per page, and the ID of the run to start the page after or before. For object fields like `page`, you should use the "form" encoding style. For example, to get the next page of runs, you can use `page[after]=run_1234`.
- **filter** (object) - Optional - Use this parameter to filter the runs. You can filter by created at, status, task identifier, and version. For array fields, you can provide multiple values to filter by using a comma-separated list. For example, to get QUEUED and EXECUTING runs, you can use `filter[status]=QUEUED,EXECUTING`. For object fields, you should use the "form" encoding style. For example, to filter by the period, you can use `filter[createdAt][period]=1d`.

### Authorizations
- **Authorization** (string, header) - Required - Use a named environment API key. It starts with `tr_dev_sk_`, `tr_prod_sk_`, `tr_stg_sk_`, etc. Create a named API key in the API Keys section of your Trigger.dev project dashboard. Choose the narrowest access preset that supports your integration. Our TypeScript SDK will default to using the value of the `TRIGGER_SECRET_KEY` environment variable if it is set. If you are using the SDK in a different environment, you can set the key using the `configure` function.

### Request Example
```
GET /api/v1/runs?limit=20
```

### Response
#### Success Response (200)
- **data** (array) - List of runs.
  - **id** (string) - The run ID.
  - **status** (string) - The status of the run.
  - **taskIdentifier** (string) - The task identifier.
  - **env** (object) - Environment details.
    - **id** (string) - Environment ID.
    - **name** (string) - Environment name.
    - **user** (string) - User associated with the environment.
  - **isTest** (boolean) - Whether the run is a test.
  - **createdAt** (string) - Creation timestamp.
  - **updatedAt** (string) - Last update timestamp.
  - **version** (number) - Version number.
  - **idempotencyKey** (string) - Idempotency key.
  - **startedAt** (string) - Start timestamp.
  - **finishedAt** (string) - Finish timestamp.
  - **delayedUntil** (string) - Delayed until timestamp.
  - **ttl** (string) - Time to live.
  - **expiredAt** (string) - Expiration timestamp.
  - **tags** (array of strings) - Tags associated with the run.
  - **costInCents** (number) - Cost in cents.
  - **baseCostInCents** (number) - Base cost in cents.
  - **durationMs** (number) - Duration in milliseconds.
- **pagination** (object) - Pagination information.
  - **next** (string) - Next page cursor.
  - **previous** (string) - Previous page cursor.

#### Response Example
```
{
  "data": [
    {
      "id": "run_1234",
      "status": "PENDING_VERSION",
      "taskIdentifier": "my-task",
      "env": {
        "id": "cl1234",
        "name": "dev",
        "user": "Anna"
      },
      "isTest": false,
      "createdAt": "2023-11-07T05:31:56Z",
      "updatedAt": "2023-11-07T05:31:56Z",
      "version": 20240523.1,
      "idempotencyKey": "idempotency_key_1234",
      "startedAt": "2023-11-07T05:31:56Z",
      "finishedAt": "2023-11-07T05:31:56Z",
      "delayedUntil": "2023-11-07T05:31:56Z",
      "ttl": "1h42m",
      "expiredAt": "2023-11-07T05:31:56Z",
      "tags": [
        "user_5df987al13",
        "org_c6b7dycmxw"
      ],
      "costInCents": 0.00292,
      "baseCostInCents": 0.0025,
      "durationMs": 491
    }
  ],
  "pagination": {
    "next": "run_1234",
    "previous": "run_5678"
  }
}
```

### Error Handling
#### Error Response (400)
- **error** (string) - Error message.
- **details** (array) - Error details.
  - **code** (string) - Error code.
  - **message** (string) - Error message.
  - **path** (array of strings) - Path to the invalid field.

#### Error Example
```
{
  "error": "Query Error",
  "details": [
    {
      "code": "custom",
      "message": "Invalid status values: FOOBAR",
      "path": [
        "filter[status]"
      ]
    }
  ]
}
```
```

--------------------------------

### installedPackagesForTarget hook example

Source: https://trigger.dev/docs/llms-full.txt

Tells build diagnostics which packages the extension installs for a given target. Only implement if the extension installs packages; the bundler ignores this hook.

```ts
{
  name: "my-extension",
  installedPackagesForTarget: (target) => {
    return target === "deploy" ? ["my-dependency"] : [];
  },
}
```

--------------------------------

### Manual config with args array

Source: https://trigger.dev/docs/mcp-introduction

Manual configuration example showing how to append CLI options to the args array in a config file.

```json
{
  "args": ["trigger.dev@latest", "mcp", "--dev-only", "--project-ref", "proj_abc123"]
}

```

--------------------------------

### Non-interactive install with --target and -y

Source: https://trigger.dev/docs/skills

Use this command for non-interactive installation in scripts or CI. Pass `--target` to choose tools and `-y` to install every skill without prompting. This example targets both claude-code and cursor.

```bash
npx trigger.dev@latest skills --target claude-code --target cursor -y

```

--------------------------------

### Go example to create a batch

Source: https://trigger.dev/docs/management/batches/create

Uses the net/http package to POST to the batches endpoint with the same JSON payload and headers.

```go
package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "https://api.trigger.dev/api/v3/batches"

	payload := strings.NewReader("{\n  \"runCount\": 2,\n  \"parentRunId\": \"<string>\",\n  \"resumeParentOnCompletion\": true,\n  \"idempotencyKey\": \"<string>\"\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("Authorization", "Bearer <token>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

```

--------------------------------

### Create chat session start action

Source: https://trigger.dev/docs/llms-full.txt

Creates a chat session start action. The external deployment id is resolved per call and stored on the session, so all runs from that session are pinned to the deployment that started it. No chat-specific setup is needed.

```ts
// app/actions.ts
"use server";
import { chat } from "@trigger.dev/sdk/ai";
import type { myChat } from "@/trigger/chat";

// No chat-specific setup: the id is discovered per call, exactly as it is for `trigger()`.
export const startChatSession = chat.createStartSessionAction<typeof myChat>("my-chat");
```

--------------------------------

### Example 5: package.json (modern mode)

Source: https://trigger.dev/docs/llms-full.txt

Package.json with Prisma 7 beta dependencies and scripts.

```json
{
  "dependencies": {
    "@prisma/client": "6.20.0-integration-next.8",
    "@prisma/adapter-pg": "6.20.0-integration-next.8"
  },
  "scripts": {
    "generate": "prisma generate",
    "dev": "pnpm generate && trigger dev",
    "deploy": "trigger deploy"
  }
}
```

--------------------------------

### BuildLayer commands property example

Source: https://trigger.dev/docs/config/extensions/custom

Shows the format for the commands property, an array of strings. Commands run after packages are installed and code is copied, so system packages cannot be installed here.

```typescript
commands: ["echo 'Hello, world!"];
```

--------------------------------

### 200 response body for GET deployment

Source: https://trigger.dev/docs/management/deployments/retrieve

Example 200 response body for the GET deployment endpoint. Shows the structure with fields like id, status, contentHash, and worker details.

```json
{
  "id": "<string>",
  "status": "PENDING",
  "contentHash": "<string>",
  "shortCode": "<string>",
  "version": "<string>",
  "imageReference": "<string>",
  "imagePlatform": "<string>",
  "externalId": "<string>",
  "externalBuildData": {},
  "errorData": {},
  "worker": {
    "id": "<string>",
    "version": "<string>",
    "tasks": [
      {
        "id": "<string>",
        "slug": "<string>",
        "filePath": "<string>",
        "exportName": "<string>"
      }
    ]
  }
}
```

--------------------------------

### Start dev servers

Source: https://trigger.dev/docs/guides/frameworks/nango

Commands to start the dev servers for the app and Trigger.dev.

```bash
npm run dev
npx trigger.dev@latest dev

```

--------------------------------

### Create chat start session action

Source: https://trigger.dev/docs/deployment/atomic-deployment

Defines a server action to start a chat session. No chat-specific setup is needed; the deployment ID is discovered per call just like for trigger().

```typescript
// app/actions.ts
"use server";
import { chat } from "@trigger.dev/sdk/ai";
import type { myChat } from "@/trigger/chat";

// No chat-specific setup: the id is discovered per call, exactly as it is for `trigger()`.
export const startChatSession = chat.createStartSessionAction<typeof myChat>("my-chat");

```

--------------------------------

### Install latest Zod 4 with bun

Source: https://trigger.dev/docs/troubleshooting-zod

Install the latest Zod 4 release to move your application to Zod 4. Review Zod's migration guide for changes to your schemas and error handling.

```bash
bun add zod@4

```

--------------------------------

### Install latest Zod 4 with pnpm

Source: https://trigger.dev/docs/troubleshooting-zod

Install the latest Zod 4 release to move your application to Zod 4. Review Zod's migration guide for changes to your schemas and error handling.

```bash
pnpm add zod@4

```

--------------------------------

### readFile tool usage example

Source: https://trigger.dev/docs/llms-full.txt

Shows how to call the readFile tool to read a file inside the skill's bundled folder. Paths are relative to the skill root and rejected if they escape via '..' or absolute paths. Output is capped at 1 MB per call.

```text
readFile({ skill: "time-utils", path: "references/timezones.txt" })
```

--------------------------------

### Install latest Zod 4 with npm

Source: https://trigger.dev/docs/troubleshooting-zod

Install the latest Zod 4 release to move your application to Zod 4. Review Zod's migration guide for changes to your schemas and error handling.

```bash
npm install zod@4

```

--------------------------------

### useRealtimeStream - Live View

Source: https://trigger.dev/docs/llms-full.txt

Example of using useRealtimeStream to start from the latest record and keep only the most recent part.

```APIDOC
## useRealtimeStream - Live View

### Description
Start from the latest record and keep only the most recent part to create a last-value view.

### Method
Hook

### Parameters
- **runId** (string) - Required - The run ID.
- **streamKey** (string) - Required - The stream key (e.g., `"frames"`).
- **accessToken** (string) - Required - Public access token.
- **from** (string) - Optional - Set to `"latest"` to start at the current tail.
- **maxParts** (number) - Optional - Set to `1` to keep only the most recent part.

### Example
```tsx
"use client";

import { useRealtimeStream } from "@trigger.dev/react-hooks";

export function LatestFrame({ runId, accessToken }: { runId: string; accessToken: string }) {
  const { parts } = useRealtimeStream<{ url: string }>(runId, "frames", {
    accessToken,
    from: "latest",
    maxParts: 1,
  });

  const frame = parts.at(-1);
  return frame ? <img src={frame.url} alt="latest frame" /> : null;
}
```
```

--------------------------------

### Install Trigger.dev SDK and Build Package with bun

Source: https://trigger.dev/docs/manual-setup

Install the SDK as a dependency and the build package as a dev dependency using bun.

```bash
bun add @trigger.dev/sdk@latest
bun add -D @trigger.dev/build@latest
```

--------------------------------

### installedPackagesForTarget hook example

Source: https://trigger.dev/docs/config/extensions/custom

Tells build diagnostics which packages the extension installs into the deployed image for a given target. The bundler ignores this hook, so it never changes build output. Only implement if the extension installs packages.

```javascript
{
  name: "my-extension",
  installedPackagesForTarget: (target) => {
    return target === "deploy" ? ["my-dependency"] : [];
  },
}

```

--------------------------------

### SKILL.md example

Source: https://trigger.dev/docs/ai-chat/patterns/skills

Example SKILL.md with YAML frontmatter (name and description required) and a body that instructs the agent when to use the skill and how to call its scripts.

```markdown
---
name: time-utils
description: Compute and format dates/times in arbitrary timezones. Use when the user asks "what time is it", timezone conversions, or date math.
---

# Time utilities

## When to use

- The user asks for the current time in a timezone
- The user wants date math ("3 days from now")

## Scripts

### `scripts/now.sh [TZ]`
Prints the current time in the given IANA timezone (default `UTC`).

### `scripts/add.sh DAYS [TZ]`
Prints a date `DAYS` days from now.

## Tips
- IANA timezone names only (`America/New_York`, not `EST`).
- See `references/timezones.txt` for a cheat-sheet.

```

--------------------------------

### Basic Playwright extension setup

Source: https://trigger.dev/docs/config/extensions/playwright

Basic setup for using the Playwright build extension in a Trigger.dev project. Automatically installs Playwright and required browser dependencies, with default options (chromium, headless, auto-detected version).

```typescript
import { defineConfig } from "@trigger.dev/sdk";
import { playwright } from "@trigger.dev/build/extensions/playwright";

export default defineConfig({
  project: "<project ref>",
  // Your other config settings...
  build: {
    extensions: [
      playwright(),
    ],
  },
});
```

--------------------------------

### Install Zod 4 with npm, pnpm, or bun

Source: https://trigger.dev/docs/llms-full.txt

Install the latest Zod 4 release to move your application to Zod 4. Review Zod's migration guide for changes to your schemas and error handling.

```bash
npm install zod@4
```

```bash
pnpm add zod@4
```

```bash
bun add zod@4
```

--------------------------------

### Prisma 7 beta (modern mode) setup

Source: https://trigger.dev/docs/config/extensions/prismaExtension

Complete setup for Prisma 7 beta (modern mode) with Trigger.dev. Includes the Prisma schema with prisma-client generator and PostgreSQL datasource, prisma.config.ts with dotenv and migrations path, package.json with @prisma/client and @prisma/adapter-pg dependencies and scripts for generate/dev/deploy, trigger.config.ts enabling modern mode, and src/db.ts creating a PrismaClient with a PrismaPg adapter using DATABASE_URL.

```prisma
generator client {
  provider = "prisma-client"
  output   = "../src/generated/prisma"
}

datasource db {
  provider = "postgresql"
}

```

```typescript
import { defineConfig, env } from "prisma/config";
import "dotenv/config";

export default defineConfig({
  schema: "prisma/schema.prisma",
  migrations: {
    path: "prisma/migrations",
  },
  datasource: {
    url: env("DATABASE_URL"),
  },
});

```

```json
{
  "dependencies": {
    "@prisma/client": "6.20.0-integration-next.8",
    "@prisma/adapter-pg": "6.20.0-integration-next.8"
  },
  "scripts": {
    "generate": "prisma generate",
    "dev": "pnpm generate && trigger dev",
    "deploy": "trigger deploy"
  }
}

```

```typescript
prismaExtension({
  mode: "modern",
});

```

```typescript
import { PrismaClient } from "./generated/prisma/client.js";
import { PrismaPg } from "@prisma/adapter-pg";

const adapter = new PrismaPg({
  connectionString: process.env.DATABASE_URL!,
});

export const db = new PrismaClient({ adapter });

```

--------------------------------

### Set up Python virtual environment and install dependencies

Source: https://trigger.dev/docs/guides/python/python-doc-to-markdown

Commands to set up a Python virtual environment and install dependencies for testing a Trigger.dev task. Requires Python 3.10 or higher.

```bash
python -m venv venv
```

```bash
source venv/bin/activate
```

```bash
venv\Scripts\activate
```

```bash
pip install -r requirements.txt
```

--------------------------------

### List errors with GET /api/v1/errors

Source: https://trigger.dev/docs/management/errors/list

Send a GET request to the List errors endpoint. The cURL example uses the TRIGGER_SECRET_KEY environment variable; other languages use a placeholder token. The endpoint returns a list of error groups.

```bash
curl -X GET "https://api.trigger.dev/api/v1/errors?filter[status]=unresolved" \
  -H "Authorization: Bearer $TRIGGER_SECRET_KEY"
```

```python
import requests

url = "https://api.trigger.dev/api/v1/errors"

headers = {"Authorization": "Bearer <token>"}

response = requests.get(url, headers=headers)

print(response.text)
```

```javascript
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.trigger.dev/api/v1/errors', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));
```

```php
<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.trigger.dev/api/v1/errors",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}
```

```go
package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.trigger.dev/api/v1/errors"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}
```

```java
HttpResponse<String> response = Unirest.get("https://api.trigger.dev/api/v1/errors")
  .header("Authorization", "Bearer <token>")
  .asString();
```

```ruby
require 'uri'
require 'net/http'

url = URI("https://api.trigger.dev/api/v1/errors")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body
```

--------------------------------

### Install Nango frontend SDK

Source: https://trigger.dev/docs/guides/frameworks/nango

Installs the Nango frontend SDK in your Next.js project. Required before using the connect session token flow.

```bash
npm install @nangohq/frontend

```

--------------------------------

### Run Trigger.dev dev server with bun

Source: https://trigger.dev/docs/llms-full.txt

Starts the Trigger.dev development server locally using bun. Use this to verify the migration by sending a message through your existing UI.

```bash
bunx trigger.dev@latest dev
```

--------------------------------

### AI setup prompt for Trigger.dev

Source: https://trigger.dev/docs/quick-start

Use this prompt with an AI coding assistant to set up Trigger.dev in a project. It instructs the assistant to run `npx trigger.dev@latest init`, install the MCP server, start the dev server, and create a Trigger-only API key. It also enforces critical rules: always import from `@trigger.dev/sdk`, never use `client.defineJob()`, and use type-only imports when triggering tasks from backend code.

```text
Help me add Trigger.dev to this project.

## What to do

1. I need a Trigger.dev account. If I don't have one, point me to https://cloud.trigger.dev to sign up. Wait for me to confirm.
2. Run `npx trigger.dev@latest init` in the project root.
   - When it asks about the MCP server, recommend I install it (best DX: gives you direct access to Trigger.dev docs, deploys, and run monitoring).
   - Install the "Hello World" example task when prompted.
3. Run `npx trigger.dev@latest dev` to start the dev server.
4. Once the dev server is running, test the example task from the Trigger.dev dashboard.
5. Create a named API key in my Development environment with **Trigger only** access. Set it as TRIGGER_SECRET_KEY in my .env file (or .env.local for Next.js).
6. Ask me what framework I'm using and show me how to trigger the task from my backend code.

If I've already run init and want the MCP server, run: npx trigger.dev@latest install-mcp

## Critical rules

- ALWAYS import from `@trigger.dev/sdk`. NEVER import from `@trigger.dev/sdk/v3`.
- NEVER use `client.defineJob()` — that's the deprecated v2 API.
- Use type-only imports when triggering from backend code to avoid bundling task code:

  import type { myTask } from "./trigger/example";
  import { tasks } from "@trigger.dev/sdk";

  const handle = await tasks.trigger<typeof myTask>("hello-world", { message: "Hello from my app!" });

## When done, point me to

- Writing tasks: https://trigger.dev/docs/tasks/overview
- Real-time updates: https://trigger.dev/docs/realtime/overview
- AI tooling: https://trigger.dev/docs/building-with-ai
```

--------------------------------

### Install specific package version with aptGet extension

Source: https://trigger.dev/docs/config/extensions/aptGet

Installs a specific version of a package by appending =<version> to the package name, e.g., "ffmpeg=6.0-4". Note that the aptGet import is omitted in this example, so it must be added for the code to work.

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

export default defineConfig({
  project: "<project ref>",
  // Your other config settings...
  build: {
    extensions: [aptGet({ packages: ["ffmpeg=6.0-4"] })],
  },
});
```
Tokens:
Raw