Chase the comments nobody answered in your docs
Every morning, WebRun opens the Quip folders your team works in, reads each document for comments and @-mentions that have no reply, records who was asked and how long ago, keeps a running index in Notion, and posts each person their outstanding items to your Microsoft Teams channel.
- 7-day free trial
- Under $0.01 per run
- Cancel anytime
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
quip.comin a real browser with your saved login - no setup, no API keys. -
1
Quip - find comments with no reply
WebRun opens Quip to find comments with no reply. - Sign in to Quip and open the shared folders your team works in
- Open each document updated in the last 30 days and read its comment threads
- Capture every thread that has no reply, along with the document, the person mentioned, and the date asked
- Work out how many days each thread has been waiting
- Skip threads already marked resolved
Done when Every unanswered comment thread is captured with its document, owner, and age.
-
2
Notion - index the open threads
WebRun opens Notion to index the open threads. - Open your open-threads database in Notion
- Create or update one record per unanswered thread with document, person, question, date asked, and days waiting
- Close out records for threads that were answered or resolved since the last run
- Group the view by person so each name has one clean list
Done when The Notion index matches the live state of open threads in Quip.
-
3
Microsoft Teams - post each person their items
WebRun opens Microsoft Teams to post each person their items. - Post the morning chase list to your team channel in Microsoft Teams
- Group the items under each person, oldest waiting first
- Give each line the document name, the question in one line, and the days waiting
- Add the total count of open threads and how it moved since yesterday
Done when Every person with an unanswered comment has their list in Teams.
How do I make sure comments in our shared docs actually get answered?
WebRun chases unanswered comments in Quip every morning. It reads the comment threads in your team's recently updated documents, records who was asked and how long ago, keeps a running index in Notion, and posts each person their outstanding items to Microsoft Teams, oldest first.
- Questions in docs get an answer instead of scrolling out of view
- Each person sees only their own outstanding items
- The open thread count is trended daily instead of guessed at
Built for project managers · operations teams · Salesforce customers using Quip · distributed 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 reply to or resolve comments for me?
No. WebRun never writes in your Quip documents. It reads the threads and reports them, and every reply or resolution is done by a person.
Does it edit the documents?
No. Quip is read only in this workflow. The only things WebRun writes are your own Notion index and the Teams post.
What if a thread was answered outside Quip?
Mark it resolved in Quip and it drops off the next run, since the list is rebuilt from the live document state rather than a stale copy.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.