Linking Hookdeck 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 Hookdeck connector syncs events, attempts, requests, 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 Hookdeck project API key to pull your webhook delivery history.
You can find the key in Hookdeck under Settings → Project → Secrets.
API keys are scoped to a single Hookdeck project, so connect one PostHog source per project. Hookdeck deletes events, requests and attempts once your plan's retention window passes, so the first sync only reaches as far back as that window.
You'll be asked for:
- API key
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 Hookdeck tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
events | Delivery records: one row per event Hookdeck queued for a connection, with its status, attempt count, error code and retry timestamps | Incremental, Full refresh | created_at | — |
attempts | Individual delivery attempts for events, including the response status, latency and error code of each try | Full refresh | — | — |
requests | Raw inbound HTTP requests received by your sources, including requests that were ignored and produced no event | Incremental, Full refresh | created_at, ingested_at | — |
issues | Grouped delivery, transformation, backpressure and request failures raised by your issue triggers | Incremental, Full refresh | created_at, first_seen_at, last_seen_at | — |
connections | Routes that tie a source to a destination, with the rules (retry, filter, transform, delay) applied in between | Full refresh | — | — |
sources | Inbound endpoints that receive webhooks from a provider, with their URL, type and verification config | Full refresh | — | — |
destinations | Endpoints Hookdeck delivers events to, with their type and delivery config | Full refresh | — | — |
transformations | JavaScript transformations that rewrite an event before it is delivered | Full refresh | — | — |
issue_triggers | Rules that decide when a delivery, transformation, backpressure or request failure is raised as an issue, and where it is notified | Full refresh | — | — |
bookmarks | Saved event payloads kept for replaying against a connection | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API 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.