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

# Linking Temporal.io as a source

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

> **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)
- [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 Temporal.io connector syncs your Temporal workflow data into PostHog, so you can analyze workflow activity alongside your product data.

## Prerequisites

You need a Temporal namespace and the mTLS client certificate and key that the namespace trusts. PostHog authenticates to your namespace's gRPC endpoint using client-certificate (mTLS) authentication.

## 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 Temporal.io, you'll need:

-   **Host** – the hostname of your Temporal namespace's gRPC endpoint, for example `your-namespace.account.tmprl.cloud` (without a protocol scheme or port).
-   **Port** – the gRPC port for your namespace, typically `7233`.
-   **Namespace** – the name of the Temporal namespace to sync.
-   **Server client root CA** – the root CA certificate (PEM) for the Temporal server, including the `BEGIN` and `END` lines.
-   **Client certificate** – your mTLS client certificate (PEM), including the `BEGIN` and `END` lines.
-   **Client private key** – the private key for your client certificate (PEM), including the `BEGIN` and `END` lines.
-   **Encryption key** *(optional)* – the key used to decrypt payloads, if your workflows use encrypted payloads.
-   **Fallback decryption keys** *(optional)* – additional decryption keys (comma-separated) for payloads encrypted with rotated keys.

## 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 |
| --- | --- | --- |
| `Host` | text | Yes |
| `Port` | number | Yes |
| `Namespace` | text | Yes |
| `Encryption key` | password | No |
| `Fallback decryption keys` | password | No |
| `Server client root CA` | textarea | Yes |
| `Client certificate` | textarea | Yes |
| `Client private key` | textarea | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `workflows` | A workflow execution in your Temporal namespace, with its type, status, and timing. | Incremental, Full refresh | CloseTime | — |
| `workflow_histories` | Individual events from the event history of each workflow execution. | Incremental, Full refresh | CloseTime | — |

## Troubleshooting

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.