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 enabled
  • Your PostHog project API key
  • 5 minutes to connect
  • Steps

    1. Connect PostHog

    Go to Settings → Integrations → PostHog. Enter your:

  • Project API key (Settings → Project → Personal API Keys in PostHog)
  • Project ID (from your PostHog URL: /project/XXXXX/)
  • Region (US or EU)
  • Specky requests read-only access to: session recordings, events, persons, and cohorts.

    2. Initial sync

    The first sync takes 10–30 minutes depending on how many recordings you have. Specky downloads session metadata and queues recordings for AI review. You'll see a progress indicator in Settings.

    3. Review your first session issues report

    Open Discovery → Session Intelligence. You'll see:

  • Clustered issues — groups of sessions with the same friction pattern
  • Instance count — how many sessions show this pattern
  • Affected users — the list of users who hit it, with their email addresses
  • Severity — High / Medium / Low based on instance count and rage-click intensity
  • AI summary — a plain-English description of what's broken and where in the flow
  • 4. Mark issues fixed and notify users

    When your engineering team fixes an issue:

  • Find the issue in Session Intelligence
  • Click Mark fixed
  • Choose whether to send the automated email: *"Hey [name], the [issue] you hit is now fixed."*
  • Specky sends personalised emails to every affected user. No manual outreach list required.

    5. Link to opportunities

    From any session issue, click Create Opportunity to log it in your Product Graph. If the same issue has been mentioned in Slack or Gong calls, Specky automatically cross-references it.

    Output

  • Clustered bug reports with instance counts (instead of watching 200 individual recordings)
  • A list of every affected user per bug
  • Automated close-the-loop emails when bugs are fixed
  • Bugs linked to your Product Graph for strategic context
  • Variations

    Sentry instead of PostHog? Same flow — connect via Settings → Integrations → Sentry. Specky reads error events and source maps.

    Pendo? Connect via the Pendo API key. Specky reads friction signals and feature adoption data.

    Don't have session recordings? Even without recordings, Specky can read PostHog events and surface drop-off patterns from your funnel data.