Automated Scribe New Guide Handoff
Every morning, WebRun opens Scribe, checks guides created or edited the day before, shares each one to the relevant team's Telegram group, and texts the process owner to review anything tagged critical or compliance.
How do I make sure new Scribe guides reach the right team?
WebRun checks Scribe every morning for guides created or edited the day before, shares each one to the relevant team's Telegram group, and texts the process owner to review anything tagged critical or compliance. New documentation reaches the people who need it the same day it's written, not weeks later.
- New guides reach the right team the same day they're written
- Critical and compliance guides get a review text automatically
- Routine how-tos share without interrupting anyone
Built for operations managers · training teams · customer support leads · compliance teams
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
scribehow.comin a real browser with your saved login - no setup, no API keys. -
1
Scribe - find guides created yesterday
scribehow.com
WebRun opens Scribe to find guides created yesterday. - Open Scribe and check guides created or edited in the last day
- Note the guide title, author, and which process it documents
- Flag guides tagged as a critical or compliance process
Done when Every guide created or edited yesterday is listed with its author.
-
2
Telegram - share the new guide
telegram.org
WebRun opens Telegram to share the new guide. - Share each new or updated guide to the relevant team's Telegram group
- Include the guide title and a short description
- Skip guides already shared
Done when Every new guide has been shared to its team's Telegram group.
-
3
Twilio - text the process owner for critical guides
twilio.com
WebRun opens Twilio to text the process owner for critical guides. - Text the process owner for any guide tagged critical or compliance
- Ask them to review it for accuracy
- Skip this step if nothing critical was created
Done when Every critical guide's owner has been texted to review it.
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 edit or publish a guide on its own?
No. WebRun only reads guides that already exist and shares them. It never creates, edits, or publishes a guide itself.
Why does only some guides get a text?
Texts are reserved for guides tagged critical or compliance, so routine how-tos don't interrupt anyone's day.
How does it know which team a guide belongs to?
It reads the process or folder the guide was saved under in Scribe and matches that to the relevant team's Telegram group.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.