Connect folders and delivery systems
Use supported connectors as an input trigger, an output destination, or both.
Connectors let a production workflow begin or end in the storage system your team already uses. A watched folder can supply new product files. An export node can return finished images and video to an approved destination.
Supported connector types include Google Drive, Microsoft OneDrive, and Adobe Experience Manager where enabled for the workspace.
Decide the connector’s job
| Job | Use | Result |
|---|---|---|
| Watch a folder | Start when a supported file appears. | The file enters the automation as input. |
| Export results | Send successful outputs to a selected folder. | Finished media lands in the destination. |
| Watch and export | Use the same provider at both ends. | Source files and results stay in one connected system. |
Connect an account
- Create or edit an automation.
- Choose a supported connector trigger or Export node.
- Sign in and grant the requested folder access.
- Select the source or destination folder.
- Save the automation.
- Run one controlled test before enabling unattended work.
When the source and destination use the same provider, the editor can reuse the connected account where supported. You can also choose a different account for delivery.
Design a safe watched folder
- Use a dedicated source folder instead of a general team drive.
- Keep unsupported files out of the watched path.
- Use stable file names that identify the product.
- Enable subfolder scanning only when the automation uses that structure intentionally.
- Test a single product before adding a batch.
The watched folder is a production interface. Treat changes to its structure like changes to an API contract.
Route by subfolder
Template Match can map source subfolder names to template tags. A file in a matching subfolder follows the template associated with that tag.
This is useful when the folder already communicates production intent, such as studio-white/ or lifestyle/. Unmatched subfolders and files at the root can be skipped, depending on the node configuration.
Configure triggers and automation nodes
Keep the connection healthy
OAuth access can expire or be revoked. When a connection requires attention, reauthenticate it before expecting new runs to start or exports to complete.
Where Google Drive service-account access is exposed, it can support a longer-lived operational connection. Scope it to the minimum folders the workflow needs.
Verify delivery
After the first run:
- Confirm the correct source file entered Glossi.
- Inspect the project and completed output.
- Confirm the expected file arrived in the destination folder.
- Check naming and folder placement.
- Review the run record for skipped or failed stages.
Do not treat a configured connector as proof of delivery. The completed run and destination file are the proof.