Linking Retently as a source
This source is currently in alpha. The interface and available tables may change.
The Retently connector syncs your customer feedback data – survey responses, customers, companies, campaigns, templates, sent surveys, and campaign reports – into the PostHog Data warehouse, so you can analyze NPS, CSAT, and CES results alongside your product data.
Prerequisites
You need a Retently account with access to the API settings. A key with read permission is sufficient – this source only performs GET requests.
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 Retently, you'll need:
- API key – create one under Settings → Integrations → API in Retently. PostHog sends it in the
X-Api-Keyheader.
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.
The feedback table supports incremental sync on the response creation date. Retently's other endpoints don't expose a reliable server-side "updated since" filter, so the remaining tables are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
customers | A customer (survey recipient) tracked in your Retently account. | Full refresh | — | — |
companies | A company aggregating customers in your Retently account, with per-company CX metrics. | Full refresh | — | — |
feedback | A survey response (NPS, CSAT, CES or star rating) submitted by a customer. | Incremental, Full refresh | createdDate | — |
outbox | A survey sent to a customer, with its delivery and response status. | Full refresh | — | — |
campaigns | A survey campaign configured in your Retently account. | Full refresh | — | — |
templates | A survey template configured in your Retently account. | Full refresh | — | — |
reports | Per-campaign aggregated survey metrics: score trend, delivery stats and per-question stats. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API key may be invalid or revoked. Generate a new key under Settings → Integrations → API in Retently, then reconnect.
- Retently rate-limits API requests to roughly 150 per minute. Syncs back off and retry automatically, but very large accounts may take a while on the first sync.
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.