Linking Userback 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
The Userback connector syncs your feedback, feedback comments, session recordings, projects, members, and workflows into PostHog, so you can analyze customer feedback alongside your product data.
Prerequisites
You need:
- A Userback account on a Premium plan (required for REST API access).
- An admin account in Userback.
- A Userback API token, created under Workspace settings → API tokens in Userback.
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 Userback, you'll need:
- API token – create one under Workspace settings → API tokens in your Userback dashboard.
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, feedback_comments, and session_recordings tables support incremental sync. feedback and feedback_comments use modified as the default cursor (with created available as an alternative), while session_recordings uses created.
The projects, members, and workflows tables do not have incremental fields and are full refresh only.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
feedback | Feedback items that users submitted through a Userback widget, portal, or integration, such as bug reports, ideas, and general feedback. | Incremental, Full refresh | modified, created | — |
feedback_comments | Comments that members and guests posted on feedback items. | Incremental, Full refresh | modified, created | — |
session_recordings | Session recordings that Userback captured of user sessions. | Incremental, Full refresh | created | — |
projects | Projects in the Userback account. Each project has its own feedback widget and feedback. | Full refresh | — | — |
members | Members of the Userback account and their roles. | Full refresh | — | — |
workflows | Workflow statuses that feedback moves through, per project. | Full refresh | — | — |
Troubleshooting
- 401 Unauthorized – Userback rejected your API token. Create a new token in Userback under Workspace settings → API tokens, then reconnect the source.
- 403 Forbidden – Userback refused API access for this token. The REST API needs a Premium plan and an admin account. Check your plan and account role, 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.