Automated Pictory Render Status Digest
Every morning, WebRun opens Pictory, checks which projects have finished rendering since the last run and which are still processing or failed, drafts a delivery email per finished video in Gmail for you to approve, and posts the ready list to your production Slack channel.
How do I know when my Pictory videos have finished rendering?
WebRun checks your Pictory projects every morning to see which finished rendering overnight. It drafts a delivery email per finished video in Gmail for you to approve, then posts the ready list to Slack with the client, length, and format, and flags any render that failed or is running long.
- Finished videos are handed off the same morning they render
- Failed renders are restarted before a client notices
- No delivery email leaves your account until you send it
Built for video editors · content agencies · marketing teams · solo creators
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.pictory.aiin a real browser with your saved login - no setup, no API keys. -
1
Pictory - check which projects finished rendering
pictory.ai
WebRun opens Pictory to check which projects finished rendering. - Sign into Pictory and open your projects list
- Note which projects finished rendering since the previous run, which are still processing, and which failed
- Capture the project name, its length, the aspect ratio, and the date it was created
- Match each project to its client or campaign using your naming convention
- Flag anything that has been processing far longer than a normal render
Done when Every project is classed as ready, still processing, or failed, and ready ones are matched to a client.
-
2
Gmail - draft the delivery email
gmail.com
WebRun opens Gmail to draft the delivery email. - Open Gmail and draft one delivery message per finished video, addressed to the client contact on file
- Include the project name, the length, the format, and where to view or download it
- Leave every message in Drafts. WebRun never sends a client email on its own
- Skip projects already delivered on an earlier run so nobody gets the same video twice
Done when One unsent delivery draft sits in Gmail for each newly finished video, with no repeats.
-
3
Slack - post the ready list
slack.com
WebRun opens Slack to post the ready list. - Post the ready list to your production channel
- Show each finished video with its client, length, and format, and note that a delivery draft is waiting in Gmail
- List failed renders and long-running projects underneath so someone can restart them
- Give a one-line count of ready, processing, and failed
Done when The production channel has today's ready list with failures called out.
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 without me?
No. Every delivery message is left as an unsent draft in Gmail with the project details filled in. You read it, adjust the wording, and send it. Nothing reaches a client on its own.
Will it publish videos anywhere?
No. WebRun never posts a video to social, never shares it publicly, and never deletes a project. It reads render status and prepares the handoff, and a person does the publishing.
What happens to a render that failed?
It is listed separately in the Slack post, along with any project stuck processing far longer than normal, so an editor can restart it rather than discovering it when the client asks.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.