Linking Inngest as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Inngest connector syncs events, function runs, cancellations, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- 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.
Enter your Inngest signing key to pull your Inngest data.
Find the signing key for your environment (it starts with signkey-) in your Inngest dashboard under Settings → Signing key. A signing key authenticates both the v1 and v2 REST APIs, so no extra scopes are required. To pull a branch environment instead, also enter its name in the Environment field.
Inngest retains event and run history for a plan-dependent window (from 24 hours up to 90 days), so schedule frequent syncs to keep a complete history in PostHog.
You'll be asked for:
- Signing key: for example
signkey-prod-....
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_attimestamp). 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.
All Inngest tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Signing key | password | Yes |
Environment | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
events | Events received by Inngest. Retention is plan-dependent (24 hours to 90 days), so sync frequently; the first sync backfills whatever your plan still retains | Append only, Full refresh | received_at | — |
function_runs | Function runs discovered via the events stream (one lookup per event). Status and output are point-in-time; a trailing window is re-read each sync so recent runs settle, but long-lived runs only update on a full refresh | Incremental, Full refresh | event_received_at | — |
runs | Every function run, including cron- and invoke-triggered runs. A trailing window is re-read each sync so recent runs settle, but long-lived runs only update on a full refresh | Incremental, Full refresh | queuedAt | — |
functions | A function defined in one of the environment's apps, with its triggers and flow-control configuration. | Full refresh | — | — |
cancellations | A bulk cancellation, stopping function runs in a time range matching an optional expression. | Full refresh | — | — |
environments | An Inngest environment (production, test, or branch). | Full refresh | — | — |
webhooks | An inbound webhook intake endpoint that transforms third-party payloads into Inngest events. The secret intake URL is not synced. | Full refresh | — | — |
event_keys | An event key used to send events to Inngest. The secret key material is not synced. | Full refresh | — | — |
signing_keys | A signing key used to authenticate Inngest API and SDK traffic. The secret key material is not synced. | Full refresh | — | — |
session_keys | An AgentKit session key: the dimension runs are grouped into sessions by. | Full refresh | — | — |
sessions | An AgentKit session: one value of a session key and the runs grouped under it. | Full refresh | — | — |
session_runs | Runs grouped by AgentKit session (one lookup per session) | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the signing key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.