Workflows
This content is for Spring ’26. Switch to the latest version for up-to-date documentation.
Workflows automate actions within Studio based on triggers and conditions you define. A workflow consists of three parts: a trigger (the event that starts the workflow), one or more conditions (rules that determine whether the workflow should proceed), and one or more actions (the tasks the workflow performs).
Triggers include events such as an asset being uploaded, moved to a specific folder, or having its attributes updated. Conditions allow you to filter which assets the workflow applies to-for example only processing images above a certain file size or assets tagged with a particular brand. Actions define what happens when the trigger fires and conditions are met, such as applying tags, sending notifications, running Studio Vision analysis, or routing assets through an approval chain.
Common workflow use cases include automatically applying tags when assets are uploaded to specific folders, sending notifications when assets are approved or rejected, triggering image recognition analysis on new uploads, and routing assets through multi-step approval chains. Workflows are configured in the Admin Area and run automatically in the background. When Spaces is enabled, workflows are scoped to individual Spaces and draw from the tenant’s total workflow allocation.
Studio Vision (workflow action)
Section titled “Studio Vision (workflow action)”Studio Vision can be triggered as a workflow action, allowing image recognition to run automatically whenever certain conditions are met. For example, you might configure a workflow that runs product identification and text detection on every image uploaded to your “Shelf Photos” folder. This removes the need for manual analysis and ensures consistent, timely processing of visual content.
The Studio Vision workflow action supports all recognition capabilities, including product identification, share of shelf analysis, text detection, and text detection groups. Results are written back to the asset’s metadata automatically.