Linking Sleekplan 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.
This source is currently in alpha. The interface and available tables may change.
The Sleekplan connector syncs users, posts, comments, 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.
Enter your Sleekplan API key to sync feedback posts, comments, votes, changelog updates, end users, and survey responses.
Create a key in Sleekplan under Settings > Developer. A key inherits the permissions of the member who created it, so create it from an account that can see every board you want to sync.
You'll be asked for:
- API key
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 Sleekplan tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Users | End users of your product who have interacted with the Sleekplan widget, including the people who submitted feedback, voted, commented, or answered a survey. | Full refresh | — | — |
Posts | Feedback posts on your board: feature requests, bug reports, and ideas, with their status, category, votes, and roadmap fields. | Full refresh | — | — |
Comments | Comments left on feedback posts, including private notes between workspace members and threaded replies. | Full refresh | — | — |
Votes | Individual votes cast on feedback posts, one row per user per post. Fetched per post, so every row carries the post it belongs to. | Full refresh | — | — |
Updates | Changelog entries, including drafts and scheduled entries, with their engagement stats. | Full refresh | — | — |
Satisfaction | Customer satisfaction (CSAT) survey responses, rated 1 to 5. A response submitted within 30 days of a previous one replaces it rather than creating a new record. | Incremental, Full refresh | updated | — |
Promoter | Net promoter score (NPS) survey responses, rated 1 to 10. A response submitted within 14 days of a previous one replaces it rather than creating a new record. | Incremental, Full refresh | updated | — |
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.