Automated Runway Render Handoffs
Every morning, WebRun signs in to Runway, reviews the generations that finished since the last run, records each clip's project, prompt notes, duration, and settings, posts the ready list to your Slack production channel, and drafts a Gmail handoff to the editor so finished work moves straight into the edit.
How do I get finished AI video renders to my editor each morning?
WebRun hands off your Runway output every morning. It collects the generations that finished overnight, records each clip's project, duration, settings, and link, posts the ready list to your Slack production channel, and drafts a Gmail handoff to the editor for review before sending.
- Finished clips reach the editor the morning they are ready
- Failed generations are caught instead of discovered mid-edit
- Every clip is handed over with the settings that produced it
Built for video production teams · creative agencies · motion designers · content studios
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
app.runwayml.comin a real browser with your saved login - no setup, no API keys. -
1
Runway - collect generations finished overnight
runwayml.com
WebRun opens Runway to collect generations finished overnight. - Sign in to Runway and open your workspace assets
- List the generations that completed since the last run, grouped by project
- Capture each clip's name, project, duration, and the settings used
- Note any generation that failed or was cancelled so it can be re-queued by a person
- Record the shareable asset link for each finished clip
Done when Every overnight generation is listed as finished or failed, with its details.
-
2
Slack - post the ready list to production
slack.com
WebRun opens Slack to post the ready list to production. - Post the ready list to your production channel
- Group clips by project with name, duration, and the asset link
- Call out failed or cancelled generations separately so someone can re-queue them
- Give the total count of clips ready to edit this morning
Done when The production channel has this morning's ready clips and the failures.
-
3
Gmail - draft the handoff to the editor
gmail.com
WebRun opens Gmail to draft the handoff to the editor. - Open Gmail and compose a handoff message to the editor from your account
- List the finished clips by project with duration, settings used, and the asset link
- Leave the message as an unsent draft so a person checks the clips before anything is sent on
Done when An unsent handoff draft is waiting in Gmail for review.
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 email the client or the editor without me?
No. The handoff sits in Gmail as an unsent draft for a person to review and send. Only the internal Slack post goes out automatically.
Does it start new generations or spend credits?
No. WebRun only reads finished work. Starting a generation, re-queueing a failure, or buying credits is always a human decision.
What happens to generations that failed?
They are listed separately in the Slack post with the project they belong to, so someone can re-queue them rather than discovering the gap during the edit.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.