Automated PostHog Session Replay Triage
Every morning, WebRun opens PostHog, filters yesterday's session replays to the ones with rage clicks or console errors, groups them by the page and the event where users got stuck, opens a Trello card per pattern with links back to the replays, and logs each pattern in Airtable so recurring friction is visible over time.
How do I turn session replays showing user friction into tickets?
WebRun triages PostHog session replays every morning. It filters yesterday's sessions to those with rage clicks or console errors, groups them into patterns by page, opens a Trello card per pattern with replay links, and logs the pattern in Airtable, so real user friction gets an owner the same day.
- Friction patterns get a card and an owner the same day
- Twelve stuck sessions become one card, not twelve
- Recurring annoyances become visible as monthly totals
Built for product managers · frontend engineers · growth teams · UX researchers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.posthog.comin a real browser with your saved login - no setup, no API keys. -
1
PostHog - find sessions where users got stuck
posthog.com
WebRun opens PostHog to find sessions where users got stuck. - Sign in to PostHog and open session replays for the last twenty four hours
- Filter to sessions containing rage clicks, dead clicks, or console errors
- For each one, note the page, the event before the friction, the browser, and the replay link
Done when Yesterday's replays showing friction are listed with their page and their link.
-
2
Trello - open a card per friction pattern
trello.com
WebRun opens Trello to open a card per friction pattern. - Group the sessions into patterns by page and by the event where users got stuck
- Open one Trello card per pattern with how many sessions hit it and two or three replay links as evidence
- Add to an existing card instead of opening a duplicate when the same pattern is already on the board
Done when Every friction pattern from yesterday has a card with replay evidence attached.
-
3
Airtable - log recurring friction over time
airtable.com
WebRun opens Airtable to log recurring friction over time. - Log each pattern in your friction base with the date, the page, the session count, and the linked card
- Increment the count when a pattern appears again, so a small daily annoyance shows as a large monthly one
- Keep a view of patterns still open after seven days so nothing quietly sits without an owner
Done when The friction base reflects yesterday's patterns and their running totals.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it open a card for every single session?
No. WebRun groups sessions into patterns by page and event first, so twelve users hitting one broken button become one card with twelve sessions behind it, not twelve cards.
Does it share user data outside our tools?
No. The card carries the page, the event, and a PostHog replay link. Anyone opening that link still needs their own PostHog access, so nothing leaves your workspace.
Can it contact the users who got stuck?
No. WebRun only creates internal Trello cards and Airtable rows for your team. Reaching out to a user is always a person's decision and a person's message.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.