Automate repeat production
Set up a sequence of steps that renders, edits and delivers product content when a folder, a workspace event or you start it.
An automation is a trigger followed by steps: for example, watch a Google Drive folder, render each new model with a template, and export the images back to Drive. Build one after the template and the output have already worked on a product you rendered by hand.
Enterprise. Automations are available on Enterprise. Only one automation can be active in a workspace at a time.
Create an automation
- Open Automations and create a new automation.
- Choose a trigger. See Choose an automation trigger.
- Add steps after the trigger, in the order the work should happen. See Add automation steps.
- Fill in every step. The automation can't run or be turned on until each step is set up.
- Select Run once to test it on the current files or models. This works while the automation is paused.
- Check the job in the Jobs list and the files in the destination.
- Turn on the switch in the header to run it automatically.
Turning one automation on pauses any other active automation in the workspace, because the workspace has one render instance for automations.
A dependable first automation is:
Google Drive -> Render -> Export to Google DriveAdd an AI Edit step only after that path works:
Google Drive -> Render -> AI Edit -> Export to Google DriveAfter you start a render on Render products, Automate this template starts an automation that keeps using that template version.
Test before turning it on
Run one representative file or model and confirm:
- the right input was picked up
- the template version you expect was used
- every shot and clip rendered
- any AI edit is acceptable
- the files reached the right destination folder
Watch it run
Each source file or model becomes a job in the Jobs list on the automation. Failed work retries automatically, and Cancel stops the active jobs. See Inspect jobs and recover failures.
Connected accounts can expire or lose access. When that happens, sign in again on the trigger or export step.
Run from an agent or the API
An agent connected to Glossi can build an automation from what you ask for, change it, run it once and follow the run until it finishes. A Manual automation can run on models the agent names instead of its saved scope. New automations are saved paused, and runs use your workspace's usage, so the agent asks before starting one. Signing in to Google Drive, OneDrive or AEM and choosing a folder stays in Glossi; the agent gives you the link.