Choose an automation trigger
Start production manually, from a connected folder, or from a supported event inside Glossi.
Every automation begins with one trigger. Choose the trigger that matches where the work becomes ready, not where it happened to be stored during testing.
Manual
Use Manual for a repeatable workflow that should run only when an operator chooses Run Now.
This is the safest place to validate a new node chain because the source scope and timing remain explicit. Depending on the workflow, you can scope a manual run to ready models, tags, or selected models.
Good fit: A producer selects a known group of prepared products and applies a tested template.
Watch Folder
Use Watch Folder when supported source files arrive in Google Drive, OneDrive, or Adobe Experience Manager.
Configure:
- the connected account
- the folder to watch
- polling interval
- maximum files processed per polling cycle
- whether existing files should be processed on the first scan
- whether modified files should be considered again
- whether immediate subfolders should be scanned
Folder triggers poll on a schedule. Detection and processing can therefore begin several minutes after a file arrives.
Use subfolders intentionally
When subfolder scanning is enabled, the immediate subfolder name can provide routing context to a Template Match node. Use stable folder names that correspond to approved template tags.
Nested folder behavior is limited. Test the exact hierarchy before relying on it for production routing.
Protect against repeated work
Glossi tracks connector file state to avoid processing every unchanged file on every poll. A modified file, restored run, or changed source configuration can still create new work. Verify run and destination state before manually replacing a connector job.
Connect folders and delivery systems
Model Ready
Use Model Ready when the workflow should begin after a model finishes supported upload, conversion, and preparation.
This trigger is useful when every new prepared model should enter the same verified render path. It does not establish that the product’s scale, regions, or materials are visually correct. Add an operating review when readiness requires more than processing success.
Project Created
Use Project Created when new projects should enter a consistent downstream render path.
The project should already contain the intended models and starting setup. Avoid attaching an automatic render to exploratory project creation unless incomplete scenes are acceptable inputs.
Render Complete
Use Render Complete to continue from a finished render into supported style, AI-edit, or export work.
Enable the available protection against outputs created by other automations when a loop could cause one generated render to trigger another workflow indefinitely.
Select with one question
Where can the system know, without interpretation, that this work is ready?
- A person knows: Manual
- A file arrival knows: Watch Folder
- Model processing knows: Model Ready
- Scene creation knows: Project Created
- A finished output knows: Render Complete