Automated Wowza Broadcast Readiness Checks
Every morning, WebRun opens Wowza, checks today's scheduled broadcasts and each stream's source connection health, syncs the schedule to Google Calendar, and posts a go or no-go readiness update to Microsoft Teams, leaving the decision to start any broadcast to a human.
How do I check that a Wowza broadcast is ready before it goes live?
WebRun checks Wowza every morning for broadcasts scheduled that day, reading each stream's source and encoder connection health. It syncs the schedule to Google Calendar and posts a go or no-go readiness update to Microsoft Teams, so a broken source connection gets caught before air time instead of during a live broadcast. Starting the stream itself always stays a human step.
- Broken source connections get caught before air time, not during it
- The team calendar always matches Wowza's real broadcast schedule
- Every scheduled broadcast has a documented go or no-go status each morning
Built for broadcasters · live event producers · streaming engineers · media companies
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.wowza.comin a real browser with your saved login - no setup, no API keys. -
1
Wowza - check today's broadcasts and stream health
wowza.com
WebRun opens Wowza to check today's broadcasts and stream health. - Open Wowza and list broadcasts scheduled for today
- Check each stream's source connection and encoder status
- Flag any broadcast with a disconnected or unhealthy source
Done when Every broadcast scheduled today has its stream health checked.
-
2
Google Calendar - sync the broadcast schedule
calendar.google.com
WebRun opens Google Calendar to sync the broadcast schedule. - Create or update a calendar event for each scheduled broadcast
- Set the event to the broadcast's start time and title
- Remove events for broadcasts that were canceled
Done when The team calendar matches Wowza's current broadcast schedule.
-
3
Microsoft Teams - post the go or no-go update
microsoft.com
WebRun opens Microsoft Teams to post the go or no-go update. - Post a go or no-go status for each broadcast scheduled today
- Name any broadcast with an unhealthy source connection
- Leave starting the actual broadcast to the streaming team
Done when The team has today's readiness update in Microsoft 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
Does WebRun start the broadcast?
No. Going live is irreversible once viewers connect, so WebRun only checks stream health and reports go or no-go. Starting a broadcast in Wowza always stays a human decision.
What makes a broadcast a no-go?
A disconnected or unhealthy source, encoder, or connection reported by Wowza itself. A healthy connection status is what earns a go.
Does the calendar update if a broadcast time changes?
Yes. The Google Calendar event is updated to match, and any canceled broadcast has its event removed the same morning.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.