Stop the frontline reading last year's policy
Every Monday, WebRun opens Blink, goes through the hub documents your frontline relies on, records when each was last updated and who owns it, matches owners to teams in Notion, and posts the stale document list to Microsoft Teams so owners can refresh what people are reading.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find internal documents that have gone out of date?
WebRun opens Blink every Monday and records when each hub document was last updated, who owns it, and how often the frontline opens it. It matches owners in Notion and posts the stale document list to Microsoft Teams grouped by owner, so shift workers act on current instructions rather than outdated ones.
- Outdated policies are found before a shift worker follows one
- Every stale document is routed to a named current owner
- Documents with no owner at all are surfaced for reassignment
Built for internal comms · HR teams · operations managers · frontline organisations
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
joinblink.comin a real browser with your saved login - no setup, no API keys. -
1
Blink - find documents going stale
joinblink.com
WebRun opens Blink to find documents going stale. - Sign in to Blink and open the hub where your documents live
- List every document with the date it was last updated
- Record the owner named on each document and the teams it is shared with
- Flag anything past your review interval, for example six months without an edit
- Note which stale documents are still being opened, because those matter most
- Check recent feed posts that point at a document, since those drive traffic to old guidance
Done when Every hub document has a last updated date, an owner, and a stale or current mark.
-
2
Notion - match each to its owner
notion.so How to Automate Notion
WebRun opens Notion to match each to its owner. - Update your document register with this week's last updated dates
- Match each owner to a current team lead, and mark documents whose owner has left
- Rank the stale list by how much the document is used, not just by age
- Keep the history so you can see the register improving month by month
Done when Every stale document has a named current owner in the register.
-
3
Microsoft Teams - route the review list
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to route the review list. - Post the review list to your internal comms channel grouped by owner
- Show each document's name, age since last update, and how often it is opened
- Call out documents with no current owner so one can be assigned
- Leave the editing to a human. WebRun never changes, republishes, or deletes a document
Done when Owners have this week's review list in Teams.
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 unpublish a document?
No. WebRun never edits a hub document, archives one, or removes it from the hub. It reports which documents are stale and who owns them, and the owner makes every change.
Does it post to the frontline feed?
No. The review list goes to your internal comms channel in Teams. Nothing is posted to the Blink feed, so shift workers are not messaged by an automation.
How does it rank which stale document matters most?
By use, not just by age. A two year old document people open every week ranks above one nobody has touched since it was written, so the review effort goes where the wrong guidance does most damage.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.