Automated UserTesting Session Tracking
Every night, WebRun opens UserTesting, lists every session completed that day, checks each one against the research team Airtable tracker, adds a row for any test missing from the base, and updates the Notion research log so the team can see what is newly synced without checking two tools by hand.
How do I keep completed UserTesting sessions synced to my research tracker?
WebRun checks UserTesting every night for sessions completed that day, compares them against your Airtable research tracker, and adds a row for any test missing from the base. It updates the Notion research log with what synced, so completed sessions never sit untracked before a researcher reviews them.
- No completed session sits untracked overnight
- The Airtable base always matches what has actually run
- Researchers start the day with a synced log, not manual bookkeeping
Built for UX researchers · research ops teams · product teams · UX agencies
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
www.usertesting.comin a real browser with your saved login - no setup, no API keys. -
1
UserTesting - list sessions completed today
- Open UserTesting and list every session completed since the last run
- Capture the test name, contributor, and completion time for each
- Note which tests already have a highlight reel or summary ready
Done when Every session completed since the last run has been captured.
-
2
Airtable - reconcile against the tracker
WebRun opens Airtable to reconcile against the tracker. - Check the Airtable research tracker for a matching row per completed session
- Add a row for any completed test missing from the base
- Mark the status field as completed with the session date
Done when The Airtable tracker has a row for every completed session.
-
3
Notion - log what synced
WebRun opens Notion to log what synced. - Update the Notion research log with the tests newly added this run
- Note which project or study each test belongs to
- Leave analysis and write ups to the researcher
Done when The Notion log reflects what was newly synced tonight.
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 summarize what testers said?
No. WebRun only tracks that a session happened and logs it, so nothing gets missed. Watching sessions and pulling insights stays with your researchers.
What happens if a session is already logged?
It is skipped. WebRun checks the Airtable tracker first and only adds a row for a session that is not already there.
Does it work across multiple studies at once?
Yes. It checks every session completed since the last run regardless of which study or project it belongs to, and logs each to its own tracker row.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.