Linking Sequenzy 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.
Contents
This source is currently in alpha. The interface and available tables may change.
The Sequenzy connector syncs subscribers, tags, lists, 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.
Create an API key in Sequenzy under Workspace Settings > API Keys with read access to subscribers, tags, lists, segments, campaigns, sequences, and analytics.
You'll be asked for:
- API key: for example
seq_live_....
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 Sequenzy tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
API keyType: password Required: True | |
Company IDType: text Required: False | Only needed with an account API key (starts with |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
subscribers | An email contact in the workspace, with status, tags, and custom attributes. | Full refresh | — | — |
tags | A tag definition used to segment subscribers and trigger automations. | Full refresh | — | — |
lists | A subscriber list, with current membership counts. | Full refresh | — | — |
segments | A saved segment: a set of filters over subscribers, with live match counts. | Full refresh | — | — |
campaigns | An email campaign (broadcast), with scheduling, delivery pacing, and audience state. | Full refresh | — | — |
sequences | An automation sequence (email workflow), with trigger, run state, and sending window. | Full refresh | — | — |
email_metrics | Per-email engagement metrics: one row per campaign and per sequence email step, with delivery funnel, conversions, and revenue. | 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.