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

# Linking Kestra as a source

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

![](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 Kestra connector syncs workflow executions, flow definitions, and trigger state from your [Kestra](https://kestra.io/) instance into the PostHog data warehouse, so you can analyze orchestration data alongside your product data.

## Prerequisites

-   A Kestra instance that's publicly reachable over HTTPS (Cloud, Enterprise, or self-hosted)
-   Your tenant ID – use `main` for Open Source, or your Cloud/Enterprise tenant ID
-   Credentials to authenticate (API token or Basic auth – see below)

## Creating credentials

Kestra supports two authentication methods. Choose the one that matches your deployment.

### API token (Cloud or Enterprise)

1.  In Kestra, go to **Settings** > **API Tokens**.
2.  Create a new token and grant **read** access to flows, executions, and triggers for your tenant.
3.  Copy the token – you'll paste it into PostHog when linking the source.

### Basic authentication (self-hosted)

If your self-hosted Kestra instance uses Basic authentication, you can enter your username and password directly in PostHog instead of an API token.

## 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.

You'll be asked for:

-   **Instance URL** – your Kestra HTTPS origin, for example `https://kestra.example.com`. Don't include a path or query string.
-   **Tenant ID** – use `main` for Open Source, or your Cloud/Enterprise tenant ID.
-   **Authentication** – select **API token** or **Basic authentication** and enter the corresponding credentials.

## 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](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

| Table | Supported modes |
| --- | --- |
| `executions` | Incremental or full refresh |
| `flows` | Full refresh |
| `triggers` | Full refresh |

The `executions` table uses `start_date` as its incremental cursor. By default, each incremental sync re-reads the previous seven days so that recently updated executions are captured. To pick up changes older than seven days, run a full refresh.

## Configuration

| Option | Description |
| --- | --- |
| `Instance URL` **Type:** url **Required:** True |  |
| `Tenant ID` **Type:** text **Required:** True | Use main for Open Source, or your Cloud or Enterprise tenant ID. |
| `Authentication` **Type:** select **Required:** True |  |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `executions` | Workflow executions with their flow, state, and timing details. | Incremental, Full refresh | start\_date | — |
| `flows` | Workflow definitions with tasks, triggers, and configuration. | Full refresh | — | — |
| `triggers` | Trigger definitions and their scheduler state. | Full refresh | — | — |

## Sync behavior

-   Execution rows use the API's default scope and lightweight response. Full task-run data isn't included.
-   Deleted or purged executions can't be recovered from the API. If executions are removed from Kestra, those rows won't reappear in PostHog.
-   Offset pagination can shift if records are deleted during a sync, which may cause rows to be skipped or duplicated in that run.

## Troubleshooting

-   **"Kestra rejected your credentials"** – your API token or Basic auth details are wrong, expired, or revoked. Create a new token in **Settings** > **API Tokens** (or check your username and password), then reconnect the source.
-   **"Kestra denied access"** – your credentials don't have read permission for the selected table. Grant read access in the Kestra tenant, then retry the sync.
-   **Older executions aren't updating** – incremental syncs only re-read the last seven days. Run a full refresh to update older execution rows.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/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.

### Still have questions?

Ask PostHog AI

### Was this page useful?

HelpfulCould be better