Linking Reply.io as a source
This source is currently in alpha. The interface and available tables may change.
The Reply.io connector syncs your sales engagement data into the PostHog Data warehouse, so you can analyze your contacts, sequences, tasks, and inbox activity alongside your product data.
Prerequisites
You need a Reply account with API access so you can create an API key. API keys are scoped, so make sure the key you use grants read access to the data you want to sync.
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.
When linking Reply.io, you'll need:
- API key – create one under Settings → API Keys in your Reply account. To sync every table, the key needs the
contacts:read,sequences:read,tasks:read,channels:read, andinbox:readscopes (or broader scopes that include them). Tables whose scope is missing can be deselected in the table picker.
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 Reply.io tables are full refresh only, since the Reply API exposes no incremental sync filter.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
contacts | A prospect (person) in your Reply account, with profile, ownership, opt-out state, and the sequences and lists they belong to. | Full refresh | — | — |
contact_lists | A named list used to group contacts in Reply. | Full refresh | — | — |
accounts | An account (company/organization) that contacts belong to in Reply. | Full refresh | — | — |
account_lists | A named list used to group accounts (companies) in Reply. | Full refresh | — | — |
custom_fields | A user-defined custom field available on contacts in Reply. | Full refresh | — | — |
sequences | A multichannel outreach sequence (email, LinkedIn, calls, tasks) in Reply. | Full refresh | — | — |
tasks | A manual task (to-do, call, meeting, LinkedIn action, manual email) assigned to a team member in Reply. | Full refresh | — | — |
email_templates | An email template used in sequences and one-off outreach in Reply. | Full refresh | — | — |
email_template_folders | A folder used to organize email templates in Reply. | Full refresh | — | — |
email_accounts | An email account connected to Reply for sending and receiving. | Full refresh | — | — |
inbox_threads | A conversation thread in Reply's unified inbox, aggregated across channels. | Full refresh | — | — |
Troubleshooting
- If you get an authorization error, your Reply API key is invalid or has been revoked. Create a new key under Settings → API Keys, then reconnect.
- If you get a permission error on a specific table, your API key is missing the scope that table requires. Grant the missing scope to the key (or create a new key with it), then reconnect.
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.