Keep the template, views, and output rules together.
Turn approved creative direction into finished assets across your 3D catalog.
Choose the approved views, lighting, motion, and output formats once. Automations apply that direction to each production-ready 3D model. Every run stays visible through delivery.
Reuse the approved direction without choosing every setting again.
Follow progress through delivery. Exceptions stay visible.
Start from a folder or the API.
Start as simple as a folder drop: Glossi watches a connected Google Drive or OneDrive folder and runs on every new 3D model. Start runs manually when you want control, or drive full catalog runs through the REST API.
See every asset move through production.
Track each run from source model to finished output. Progress, errors, retries, and results stay in one place, so your team can step in quickly and keep the catalog moving.
Deliver files where your team works.
Deliver through supported connectors or the public API. Glossi makes the content, then returns the files to a supported destination.

Render the full image and video set.
Automations render stills and video in the output formats you set. Every result stays attached to its run.
Commerce still
Channel cropRun production from your own systems.
Everything above is also callable directly. Send 3D models and a template in one request: Glossi creates a project per model, renders your saved views, and returns a signed URL for every finished file. Webhooks report progress, so a PIM, DAM, or internal tool can run a whole catalog without a person watching.
{
"models": [
{ "fileName": "trail-shoe.glb", "fileType": "glb" }
],
"templateId": "your-template-uuid",
"renderSettings": { "renderBookmarks": true },
"webhookUrl": "https://acme.com/hooks/glossi"
}
Questions
Details for production teams.
What are Glossi Automations?
An Automation is a saved production setup: a trigger, project creation from a template, rendering, optional AI styles, and delivery. It runs across your 3D models in the background.
Can automations run in the background?
Yes. Runs continue in the background. Status, errors, retries, and output links stay visible for review.
How can an automation run start?
A run can start manually, from a connected Google Drive or OneDrive folder, or through the Glossi REST API.
Where can automations deliver files?
Glossi supports Google Drive, OneDrive, Adobe Experience Manager, and the public API.
Build your first Automation.
Bring a folder of 3D models and the template you saved in Studio.