Track every episode through Alitu's pipeline
Every morning, WebRun opens Alitu, checks which episodes have finished auto-editing and which are still queued, archives each finished file to Google Drive, and posts a Slack update naming what's ready to schedule.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track episodes moving through Alitu's auto-editing pipeline?
WebRun checks Alitu every morning for episodes moving through auto-editing, noting which have finished processing and which are still queued. It archives each finished episode file to Google Drive and posts a Slack update naming what's ready to schedule, so a processed episode never sits unnoticed before it's released.
- Processed episodes never sit unnoticed before release
- Finished files are backed up to Drive automatically
- The team always knows what's ready to schedule
Built for independent podcasters · podcast producers · solo creators · podcast networks
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
alitu.comin a real browser with your saved login - no setup, no API keys. -
1
Alitu - check pipeline status
alitu.com
WebRun opens Alitu to check pipeline status. - Open Alitu and check episodes currently in the auto-editing pipeline
- Note which have finished processing and which are still queued
- Capture the final episode length once processing completes
Done when Every episode in the pipeline has its current processing status.
-
2
Google Drive - archive the finished file
drive.google.com How to Automate Google Drive
WebRun opens Google Drive to archive the finished file. - Save a copy of each finished episode file to your production folder
- Name it with the episode number and date
- Skip episodes already archived
Done when Every finished episode is archived in Drive.
-
3
Slack - post the ready-to-schedule update
slack.com How to Automate Slack
WebRun opens Slack to post the ready-to-schedule update. - Post an update naming episodes that finished processing and are ready to schedule
- Note any episode still stuck in the queue
- Leave actually scheduling the release to your team
Done when The team knows which episodes are ready to schedule in Slack.
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 schedule the episode for release?
No. WebRun only tracks processing status and archives the finished file. Scheduling the release in Alitu is left to your team.
What if an episode is stuck in the queue?
It's noted in the Slack update so your team knows to check it, rather than assuming it's simply still processing normally.
Where does the finished audio file go?
Into your production folder in Google Drive, named with the episode number, as a backup outside Alitu.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.