Connect PostHog to Specky.
Bring funnels, feature flags, and survey responses beside the customer language that explains them.
Signal in
Activity
Context
Linked
Next move
Citable
What PostHog does
The tool, in plain language.
PostHog shows what people do in a product through events, funnels, retention, feature flags, surveys, cohorts, and session recordings.
Why connect it to Specky?
Keep the useful context attached.
Connect PostHog when the important question is not only what users said, but whether the behaviour changed after you shipped.
- Signup and activation questions
- Feature adoption and retention
- Connecting behaviour to customer language
The job this connection does
Why would a product team connect PostHog?
Make the useful context in PostHog available when you need to answer a product question.
Specky pulls from PostHog on a schedule
Specky checks PostHog for new activity when your workspace syncs. You can also run a sync yourself whenever you need a fresh read.
Know what this connection is for.
A useful integration is clear about its boundary: what Specky can receive, what it returns to your product workflow, and what it deliberately does not do.
You provide
- Records Specky can read from PostHog
- The credential and optional filters shown in the connect form
Specky gives back
- Typed, searchable evidence in the Product Graph
- Source-linked context for synthesis, decisions, and PRDs
A real example
Specky imports accessible records from PostHog, preserves their source context, and makes them available beside your other product evidence.
Questions you can ask in plain English
These are the kinds of questions this connection helps answer. Specky keeps the source attached so the answer can be checked, not just trusted.
Connecting PostHog
Here’s the quick version. The setup guide walks through every field and screen.
- 1
Go to your PostHog project → Settings → Personal API Keys
- 2
Click "Create personal API key"
- 3
Give it a label like specky-integration
- 4
Copy the generated key (starts with phx_)
- 5
Go to Settings → Project in PostHog
Before you connect
Personal API KeyRequired
Personal API key from your PostHog project settings.
Project IDRequired
Your PostHog project ID, found in Project Settings.
PostHog HostOptional
PostHog Cloud US (default) or EU, or your self-hosted URL.
Find the PostHog signal without the scavenger hunt
Ask about PostHog in plain English instead of digging through another tab
See recurring themes alongside signals from the rest of your stack
Carry the useful quote or record straight into a PRD or decision
Keep the original source attached so someone else can check it
Before you connect it
How does Specky use my PostHog data?
It becomes part of your Product Graph, where you can search it alongside related feedback from the rest of your stack. The source stays attached, and your workspace data is not used to train AI models.
Will Specky import my existing PostHog history?
Yes. The first sync brings in recent PostHog history, then Specky keeps up with new activity after that.
What do I need before I connect PostHog?
You will need Personal API Key, Project ID from your own PostHog account. The setup guide walks you through each one.
How long will this take?
Usually a few minutes. You create a credential in PostHog, paste it into Specky, and you are connected. Step-by-step instructions are in the setup guide.
Can I disconnect PostHog later?
Yes — go to Settings → Integrations whenever you want. Disconnecting removes the connection and the data it brought in.
Can I use PostHog on my plan?
Every plan can connect integrations. Your plan sets how many can be active at once, and a few providers are limited to Scale. Settings → Usage shows where you stand.
Bring PostHog into your product graph
Connect it in a few minutes, then let Specky do the reading.