Import Sleekplan feedback, votes, comments, changelog entries and CSAT and NPS responses into PostHog, then query them next to your product analytics.

Overview

PostHog's data warehouse imports your Sleekplan workspace: feedback posts, votes, comments, changelog entries, end users, and CSAT and NPS responses. With that data sitting next to your product analytics, you can answer questions neither tool answers on its own. Do the customers who voted for a feature actually use it after it ships? Are your most-requested ideas coming from your most active users? How does NPS differ between power users and everyone else?

How it works

PostHog connects with a Sleekplan API key and reads seven tables: Users, Posts, Comments, Votes, Updates (your changelog), Satisfaction (CSAT, rated 1 to 5) and Promoter (NPS, rated 1 to 10). The connection is read-only and runs one way. Nothing is written back to Sleekplan.

Votes arrive as one row per user per post, so you can see exactly who asked for what. The Users table carries the ID you pass to the Sleekplan widget along with the user's email. If you identify users in Sleekplan with the same ID you use in PostHog, you can join every vote, comment and survey response to that person's product events with SQL.

Posts, comments, votes, changelog entries and users reload in full on each sync. CSAT and NPS responses can sync incrementally instead. You choose which tables to import and how often they sync.

Configure

In Sleekplan, create an API key under Settings → Developer. A key has the permissions of the member who created it, so create it from an account that can see every board you want to sync.

In PostHog, open Data pipeline → Sources, click New source, pick Sleekplan and paste the key. Choose the tables, the sync method and the frequency, then click Import. PostHog's setup wizard can also detect Sleekplan in your codebase and connect it for you. PostHog built this source and lists it as alpha, so the available tables may still change.