Automated MASV Delivery Handoff Alerts
Every few minutes, WebRun checks your MASV portal for newly completed deliveries, posts the file details to the receiving editor in Slack, and sends a Telegram ping for anything tagged rush.
How do I make sure a completed MASV delivery reaches the right editor right away?
WebRun checks your MASV portal every few minutes for transfers that finish uploading, posting the file details and download link to the assigned editor in Slack. Anything tagged rush also gets an urgent Telegram ping, so a completed delivery reaches the right person within minutes instead of sitting unnoticed in the portal.
- Completed deliveries reach the right editor within minutes
- Rush files get a separate urgent alert, not buried in Slack
- Every project's full team is tagged, not just one person
Built for video editors · post-production studios · broadcast teams · media production 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
masv.ioin a real browser with your saved login - no setup, no API keys. -
1
MASV - check for completed deliveries
masv.io
WebRun opens MASV to check for completed deliveries. - Check the portal for transfers that finished uploading since the last run
- Read the sender, file size, and project tag for each
- Note anything tagged rush or urgent
Done when Every newly completed delivery since the last check is captured.
-
2
Slack - notify the receiving editor
slack.com
WebRun opens Slack to notify the receiving editor. - Post the delivery details to the project channel
- Tag the editor assigned to that project
- Include the download link and total file size
Done when The receiving editor has been notified in Slack.
-
3
Telegram - ping rush deliveries
telegram.org
WebRun opens Telegram to ping rush deliveries. - Send an urgent ping only for deliveries tagged rush
- Include the project name and who it's from
- Skip anything not marked urgent to avoid noise
Done when Rush deliveries 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 download or move the delivered files anywhere?
No. WebRun only reads delivery status and notifies your team. Downloading or filing the media is left to the editor.
How does it know what's a rush delivery?
It reads the rush or urgent tag set on the transfer in MASV, so the escalation matches what the sender actually flagged.
What if two editors are on the same project?
It tags everyone assigned to the project in Slack, so a delivery never lands with just one person who happens to be offline.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.