Automated Castos Transcript Readiness Alerts
Every morning, WebRun opens Castos, checks episodes scheduled to publish in the next 2 days for a completed transcript, posts a status update to Telegram, and texts you by Twilio if one is within 4 hours of publishing without a transcript.
How do I make sure Castos episodes have a transcript before publishing?
WebRun checks Castos every morning for episodes scheduled to publish in the next two days, confirming each has a completed automatic transcript. It posts a Telegram status update for the team, and texts you by Twilio only when an episode is within four hours of publishing with no transcript yet, so an episode never goes out without one by accident.
- No episode publishes without a transcript by accident
- The team sees transcript status without opening Castos
- Only real publish-time risk triggers a direct text
Built for podcast producers · accessibility teams · podcast networks · independent podcasters
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
castos.comin a real browser with your saved login - no setup, no API keys. -
1
Castos - check transcript status
castos.com
WebRun opens Castos to check transcript status. - Open Castos and list episodes scheduled to publish in the next 2 days
- Check each for a completed automatic transcript
- Note any episode still processing
Done when Every episode publishing soon has its transcript status recorded.
-
2
Telegram - post the status update
telegram.org
WebRun opens Telegram to post the status update. - Post a status update listing episodes still missing a transcript
- Include their scheduled publish time
- Post nothing when every upcoming episode is fully transcribed
Done when The team knows the transcript status of every episode publishing soon.
-
3
Twilio - text you on a publish risk
twilio.com
WebRun opens Twilio to text you on a publish risk. - Text yourself only when an episode is due to publish within 4 hours and still has no transcript
- Include the episode name and publish time
- Leave deciding whether to delay to you
Done when You're texted about any episode at real risk of publishing without a transcript.
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 it generate the transcript itself?
No. WebRun only checks whether Castos has finished generating it. Transcription itself runs inside Castos.
Does it delay the episode from publishing?
No. It only alerts you. Delaying or adjusting the publish time in Castos is a decision you make.
How close to publish time does the text alert fire?
Only inside 4 hours of the scheduled publish time, so routine processing delays stay in Telegram and don't interrupt you directly.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.