Automated DaVinci Resolve Render Job Alerts
Every hour, WebRun checks the DaVinci Resolve render queue, logs each finished or failed job to a running Airtable history with its project name, duration, and outcome, and emails the editor the result the moment their render completes.
How do I get notified when a DaVinci Resolve render finishes or fails?
WebRun checks the DaVinci Resolve render queue every hour, logging each finished or failed job to a running Airtable history with its project name, duration, and outcome. The moment a render completes, it emails the editor the result, including the error message on a failure, so no one has to keep checking back manually.
- Editors hear about finished or failed renders within the hour
- Failed renders come with the actual error, not just a status
- The studio keeps one running history of every render job
Built for Video editors · post-production studios · colorists · render farms
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.blackmagicdesign.comin a real browser with your saved login - no setup, no API keys. -
1
DaVinci Resolve - check the render queue
blackmagicdesign.com
WebRun checks the render queue. - Open the render queue
- Check the status of every job since the last check
- Note which finished, which failed, and why
Done when Every render job's current status is known.
-
2
Airtable - log each render job
airtable.com
WebRun logs each render job in Airtable. - Add a row per completed or failed job to the render log
- Include the project name, duration, and outcome
- Keep a running history for the studio
Done when Every render job this hour is logged with its outcome.
-
3
Gmail - email the editor the result
gmail.com
WebRun emails the editor the render result. - Email the editor when their render finishes or fails
- State the outcome and, for failures, the error reported
Done when The editor knows their render is done without checking back manually.
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 restart a failed render automatically?
No. WebRun only reports the failure and the error message. Restarting or fixing the project stays a manual step for the editor.
How often does it check the queue?
Every hour, so an editor never waits more than an hour to hear a long render finished, without needing to babysit the queue.
Does the render log include every project, or just mine?
Every job in the shared queue gets logged to Airtable, so the whole studio has one history, while the email goes only to that job's editor.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.