Follow the recipe once, then keep the parts that help.
Use the situation as your starting point, follow the steps, and save the parts that become a habit.
Try saying
“I am in this situation. Walk me through the recipe and tell me what good looks like.”
Name the situation
Start with the real moment you are in.
Follow the recipe
Do one step, then check the result.
Make it yours
Save the workflow when it works.
Set up session issues with PostHog
Situation
Your PostHog is full of session recordings that nobody has time to watch. Bugs are getting reported by support weeks after users first hit them. You want the AI to do the watching and surface what matters.
What you need
- A PostHog account with session recordings turned on
- A PostHog personal API key and your project ID
- A few minutes to connect
Steps
1. Connect PostHog
Open Connect tools, find PostHog, and enter:
- Personal API Key: create it in PostHog under Settings → Personal API Keys. It starts with
phx_. - Project ID: shown at the top of Settings → Project in PostHog.
- PostHog Host (optional): US Cloud is the default. Use
https://eu.posthog.comfor EU Cloud, or your own URL if you self-host.
2. Let the first sync run
Specky starts a sync when you connect. Use Sync now on the PostHog card to run another one later. Each sync brings in your most recent session recordings (up to 25) along with events, funnels, and surveys. Specky has AI review the recordings, starting with the ones most likely to show a problem, such as sessions with errors or rage clicks. Each analysis run uses one AI generation from your plan.
3. Review your first session issues
Session Issues is a beta view. In the sidebar, click Try beta features, then open Session Issues under Labs. You'll see:
- Issues: groups of sessions that hit the same problem, sorted by severity
- Instances: how many sessions show this problem
- Affected users: the PostHog IDs or emails of the people who hit it
- Severity: critical, high, medium, or low, rated by the AI review. An issue takes the severity of its most serious instance.
- Summary: a plain-English description of what is broken
Click an issue to see each instance with its steps, evidence, and a Watch session replay button.
4. Turn an issue into a ticket
Click Create ticket on an open issue. Specky opens the chat with the issue's title, summary, severity, and counts, and drafts an engineering ticket from them.
5. Mark issues fixed
When your engineering team ships the fix:
- Find the issue under Open
- Click Mark fixed
- Confirm with Mark fixed in the dialog
The issue moves to the Fixed filter. Specky does not email affected users when you mark an issue fixed, so tell them yourself if you want to close the loop.
Output
- Grouped bug reports with instance counts, instead of hundreds of separate recordings
- The affected users for every issue
- Engineering tickets drafted straight from an issue
- A clear split between open and fixed issues
Variations
Sentry instead of PostHog? Same flow. Connect Sentry in Connect tools with an Auth Token, Organization Slug, and Project Slug. Specky reviews new errors the same way.
Pendo? Connect Pendo in Connect tools. Specky reviews Pendo feedback, page drop-offs, and guides as friction signals.
Don't have session recordings? Session Issues only reviews PostHog recordings, not plain events. Open Funnel analytics instead to see your saved PostHog funnels and the step where the most people drop off.
Ready to apply this?
Start with your own product and keep the first read grounded. You'll create an account before the guided result so it can be saved to your workspace.