Automated Luma AI Generation Handoff
Every few minutes, WebRun checks Luma AI for generations that just finished, saves each one into an organized Google Drive folder by project, and posts a Slack message to your creative channel with a preview link for a teammate to review.
How do I get finished Luma AI generations reviewed by my team quickly?
WebRun checks Luma AI every few minutes for finished generations, saves each one into an organized Google Drive folder by project, and posts a Slack message tagging the teammate who owns that project with a preview link. Nothing gets published or shared outside the team until that teammate approves it.
- New generations reach a teammate for review within minutes
- Every file is saved and organized by project automatically
- Nothing goes public without a teammate's sign off
Built for creative teams · video producers · marketing agencies · 3D artists
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
lumalabs.aiin a real browser with your saved login - no setup, no API keys. -
1
Luma AI - find finished generations
lumalabs.ai
WebRun opens Luma AI to find finished generations. - Open Luma AI and check for generations that finished since the last run
- Capture the prompt, project, and generation type for each
- Skip anything still processing
Done when Every finished generation this run has been identified with its details.
-
2
Google Drive - save and organize the files
drive.google.com
WebRun opens Google Drive to save and organize the files. - Open the shared project folder in Drive
- Save each finished file with the prompt and date in its name
- Sort into subfolders by project so nothing gets buried
Done when Every finished generation is saved to Drive and organized by project.
-
3
Slack - hand off to a teammate for review
slack.com
WebRun opens Slack to hand off to a teammate for review. - Post a message to the creative channel with a link to the new file
- Tag the teammate who owns that project
- Ask for a thumbs up before it is used anywhere public
Done when A teammate has a review request in Slack for every new generation.
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 publish the video or 3D capture anywhere?
No. It only saves the file to Drive and asks a teammate to review it in Slack. Publishing or sharing externally is always a separate, human decision.
How does it know which teammate to tag?
Each project in the Drive folder maps to an owner. WebRun tags whoever owns the project the generation belongs to.
What if a generation is still processing?
It is skipped and picked up on the next check a few minutes later, so nothing incomplete gets handed off.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.