> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Trigger.dev as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/trigger-dev

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The [Trigger.dev](https://trigger.dev) connector syncs your task run history, schedules, and queues into PostHog, so you can analyze background-job execution data alongside your product analytics.

## Prerequisites

You need a Trigger.dev project and a secret API key for the environment you want to sync. API keys are per environment (dev, staging, prod), so one connection syncs one environment. Self-hosted Trigger.dev instances are also supported.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking Trigger.dev, you'll need:

-   **Secret API key** – copy the secret key for the environment you want from your Trigger.dev project's [API keys page](https://trigger.dev/docs/apikeys). Keys are prefixed by environment: `tr_prod_...`, `tr_stg_...`, or `tr_dev_...`.
-   **API URL** *(optional)* – leave blank for Trigger.dev Cloud. If you self-host, set it to your instance's API URL (must be HTTPS).

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `runs` | A single execution of a task, with status, timings, and cost | Incremental on `createdAt` |
| `schedules` | Schedules that trigger tasks on recurring cron expressions | Full refresh |
| `queues` | Task queues with live concurrency and depth counters | Full refresh |

**Incremental** syncs on the `runs` table use a 3-day lookback window. Runs are created with an immutable `createdAt` timestamp, but fields like `status` and `costInCents` keep updating after creation. The lookback re-reads recently created runs each sync to pick up those late changes. Merge deduplication on the run `id` prevents duplicates.

**Full refresh** tables (`schedules` and `queues`) reload all data on each sync. These are typically small and have no stable timestamp to sync on.

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Secret API key` | password | Yes |
| `API URL (self-hosted only)` | text | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `runs` | A single execution of a Trigger.dev task, with its lifecycle status, timings, and cost. | Incremental, Full refresh | createdAt | — |
| `schedules` | A schedule that triggers a task on a recurring cron expression. | Full refresh | — | — |
| `queues` | A task queue and its live concurrency and depth counters. | Full refresh | — | — |
| `errors` | A group of failed runs that share an error fingerprint within one task, with its lifecycle state. | Full refresh | — | — |
| `deployments` | A deployment of the project's tasks to the environment, with its worker version and status. | Incremental, Full refresh | createdAt | — |
| `waitpoint_tokens` | A waitpoint token that pauses a run until an external system or a person completes it. | Incremental, Full refresh | createdAt | — |
| `run_events` | An OpenTelemetry span or log event recorded during a run. | Incremental, Full refresh | \_runs\_createdAt | — |

## Troubleshooting

-   If runs stop syncing with an authorization error, the API key was likely rotated or belongs to a different environment. Generate a fresh secret key for the correct environment and reconnect.
-   Each API key is scoped to a single environment (dev, staging, or prod). Make sure you're using the key for the environment you want to sync.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.