Automated Consensus Weekly Research Digest
Every Monday, WebRun opens Consensus, runs your saved research questions, reads the top papers and the consensus meter for each, posts a summary of the findings to Microsoft Teams, and books a short review slot on Google Calendar for the team to discuss what changed.
How do I keep a research question's evidence base current every week?
WebRun runs your saved research questions through Consensus every Monday, reading the top papers and the consensus meter for each, and posts a findings summary to Microsoft Teams flagging anything that shifted since last week. It books a short review slot on Google Calendar too, so evidence-based questions get revisited on a schedule instead of once and forgotten.
- Evidence gets revisited weekly instead of going stale after one search
- Shifts in the research consensus get flagged, not missed
- A review slot is booked automatically ahead of planning meetings
Built for Research teams · product teams · policy analysts · academic 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
consensus.appin a real browser with your saved login - no setup, no API keys. -
1
Consensus - run the saved research questions
WebRun runs the saved research questions in Consensus. - Open Consensus and run each saved research question
- Read the top papers and the consensus meter reading
- Note anything that changed since last week
Done when Every saved question has a current findings summary.
-
2
Microsoft Teams - post the findings summary
WebRun posts the findings summary in Microsoft Teams. - Post the findings summary for each question
- Include the consensus meter reading and top paper links
- Flag any question where the consensus shifted
Done when The team has this week's findings summary in Teams.
-
3
Google Calendar - book the review slot
WebRun books the review slot on Google Calendar. - Book a short review slot for the research lead
- Attach the findings summary to the event
- Set it before the team's next planning meeting
Done when A review slot exists ahead of the next planning meeting.
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
Does it write conclusions or make decisions for the team?
No. WebRun only summarizes what Consensus found. Interpreting the evidence and making a decision stays with your team in the review slot.
How current is the research?
Whatever Consensus itself has indexed at the time of the run, refreshed with each weekly check.
Can I add or remove research questions it tracks?
Yes. Update your saved questions in Consensus and the next run picks up the change automatically.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.