Automated Restream Pre-Stream Checks
Every morning, WebRun signs in to Restream, looks at the broadcasts scheduled for today, checks that every destination channel is still connected and that each has a title and description set, posts the readiness checklist to Slack, and sends the producer a short go or no-go on Telegram.
How do I check my multistream setup is ready before going live?
WebRun checks your Restream broadcasts scheduled for today every morning, confirming each destination channel is still connected and that every one has a title and description set. It posts a per-channel readiness checklist to Slack and sends the producer a Telegram go or no-go naming any problem.
- Disconnected destinations are caught hours before going live
- Every platform gets a title instead of streaming untitled
- The producer starts the day with a clear go or no-go
Built for live streamers · production teams · church and event AV teams · creator agencies
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
restream.ioin a real browser with your saved login - no setup, no API keys. -
1
Restream - check today's broadcast setup
restream.io
WebRun opens Restream to check today's broadcast setup. - Sign in to Restream and open the events scheduled for today
- List every destination channel attached to each event
- Check each channel still shows as connected rather than needing reauthorisation
- Check the title and description are filled in for every destination, not just the first
- Note the scheduled start time and whether the event is still set to go live
- Read only. Do not start, stop, or edit a broadcast
Done when Every scheduled broadcast has each channel marked ready or not ready.
-
2
Slack - post the readiness checklist
slack.com
WebRun opens Slack to post the readiness checklist. - Post today's readiness checklist to your production channel in Slack
- List each broadcast with its start time and every destination underneath
- Mark each channel ready, needs reconnecting, or missing a title
- Put the problems at the top so the fix list is the first thing read
Done when The production team has a per-channel checklist for every broadcast today.
-
3
Telegram - send the producer a go or no-go
telegram.org
WebRun opens Telegram to send the producer a go or no-go. - Send the producer a short go or no-go message on Telegram
- Say go when every channel is connected and titled
- Say no-go and name the exact channel and the exact problem otherwise
- Include the first scheduled start time so the fix window is obvious
Done when The producer knows before the day starts whether anything needs fixing.
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
Can it start a stream or reconnect a channel by itself?
No. WebRun only reads the setup in Restream. It never goes live, ends a broadcast, edits a title, or reauthorises a destination. Reconnecting a channel needs your own account permission, so it is always a human step.
Why check titles on every destination?
Because a title set on one platform does not always carry to the rest, and an untitled stream loses discovery on the very channels you multistream for. The checklist marks each destination separately so gaps are obvious.
What happens on a day with nothing scheduled?
You get a one line Telegram note saying there is nothing on, and no checklist is posted to Slack, so quiet days stay quiet.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.