Automated Hightail Review Deadline Chasing
Every morning, WebRun opens Hightail, checks every space sent for review, finds files with no comments or approval after 3 days, posts the full list to Slack, and sends the most overdue ones to Telegram.
How do I chase creative files that are stuck waiting on feedback?
WebRun checks every Hightail space each morning for files sent for review that still have no comments or approval after 3 days. It posts the full backlog to Slack with each reviewer named, then sends a Telegram alert for the most overdue files, so stalled creative reviews get chased before a deadline slips.
- Stalled reviews surface every morning instead of at the deadline
- Reviewers get named in the chase list, not just the file
- Cleared reviews drop off the list automatically
Built for creative teams · marketing teams · agencies · brand managers
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.hightail.comin a real browser with your saved login - no setup, no API keys. -
1
Hightail - find files awaiting feedback
WebRun opens Hightail to find files awaiting feedback. - Open each active space and check files sent for review
- Note which have no comments or approval and how many days they have waited
- Sort by days waiting, oldest first
Done when Every file awaiting review has a current wait time.
-
2
Slack - post the chase list
WebRun opens Slack to post the chase list. - Post the full list of files awaiting feedback to the creative channel
- Include the reviewer's name and days waiting for each
- Leave the actual review to the assigned reviewer
Done when The team has today's full review backlog in Slack.
-
3
Telegram - flag the most overdue
WebRun opens Telegram to flag the most overdue reviews. - Send a short alert for files waiting more than 3 days
- Name the reviewer holding up each one
- Skip anything already reviewed since the Hightail check
Done when The most overdue reviews have been flagged on Telegram.
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 approve or comment on files for the reviewer?
No. WebRun only reads each file's review status. Leaving feedback or approving a file is left entirely to the assigned reviewer.
How is a file marked overdue?
Anything with no comment or approval 3 days after it was sent for review, so the threshold matches how your team actually works.
What happens once a file gets feedback?
It reads the live status in Hightail each morning, so anything reviewed since the last check drops off the list automatically.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.