Linking Featurebase as a source
This source is currently in alpha. The interface and available tables may change.
The Featurebase connector syncs your customer feedback data – posts, boards, comments, upvoters, changelogs, companies, and contacts – into the PostHog Data warehouse, so you can rank feature demand and join feedback against your product usage data.
Prerequisites
You need a Featurebase account with access to create an API key. API keys are managed in the Featurebase dashboard.
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 Featurebase, you'll need:
- API key – create one in your Featurebase dashboard under Settings → API.
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.
Posts, comments, and changelogs support incremental sync. Everything else syncs via full refresh.
The post_voters table is off by default because it makes one request chain per post – enable it when you want to join upvoters against companies and contacts to rank feature demand by customer.
Webhooks
PostHog automatically registers a Featurebase webhook for you using your API key, including its signing secret, so post, comment, and changelog changes stream into the warehouse in real time between scheduled syncs after the initial backfill completes.
Featurebase caps the number of webhooks per organization (10 by default). If registration fails because you're at the cap, remove an unused webhook in Featurebase under Settings → Webhooks, or set the webhook up manually using the URL PostHog shows and paste its signing secret into the source configuration.
Deleted posts and comments aren't removed by webhooks – run a full refresh to reconcile deletions.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
posts | User-submitted feedback items. Each post belongs to a board and carries a status, tags, upvotes, comments, and custom field values. | Webhook, Incremental, Full refresh | updatedAt, createdAt | — |
comments | Threaded discussions on posts and changelogs, with voting metrics and moderation flags. | Webhook, Incremental, Full refresh | createdAt | — |
changelogs | Release notes and product updates, with per-locale translations, categories, and publishing state. | Webhook, Incremental, Full refresh | date | — |
boards | Boards (post categories) that contain feedback posts, with access controls and feature toggles. | Full refresh | — | — |
post_statuses | Workflow statuses posts move through (e.g. In Review, Planned, Completed). | Full refresh | — | — |
custom_fields | Custom field definitions configured in the organization, attached to boards and filled per post. | Full refresh | — | — |
admins | Admin users of the organization's Featurebase workspace. | Full refresh | — | — |
companies | Companies tracked in Featurebase, typically synced from your own systems, with spend and plan attributes for feedback prioritization. | Full refresh | — | — |
contacts | Contacts (customers and leads) who interact with your Featurebase organization. | Full refresh | — | — |
post_voters | Maps which users upvoted which post as one row per (post, voter). Costs one request chain per post, so it's off by default | Full refresh | — | — |
Troubleshooting
- If you see an
Invalid API Keyerror, your API key is invalid or has been revoked. Create a new key in your Featurebase dashboard under Settings → API, 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.