Linking Temporal.io as a source

Contents

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 of the data pipeline section.
  2. Click + New source and click Link next to this source.
  3. Enter your credentials (see 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 for a full explanation of how each mode works and how to choose between them.

Configuration

Supported tables

The tables available from this source are discovered from your account when you connect it, so the exact list depends on your data. Once connected, you can pick which tables to sync from the sources tab.

Troubleshooting

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.

Was this page useful?