Introduction to Actions (Studio for Teams & Studio for Enterprise)

Studio workflows slow down when work is split across tools. Images are captured in Capture One, then exported, uploaded, processed elsewhere, and reviewed later. This delay pushes decisions away from the shoot and increases rework. Teams end up managing files instead of evaluating results. The more ambitious the brief, the more decisions depend on seeing the result while the set is still live. Creative work needs confidence on set, not hope in post.

Contents

• What are Actions?
• Who are Actions for?
• How do Actions work?
• Supported services
• Next steps

What are Actions?

Actions are predefined workflow steps that send images from Capture One to external services and return results back into the session. Each Action is configured once and reused across teams, ensuring consistent output without repeated setup.

From the user’s perspective, Actions behave like native Capture One features. There is no need to export files, upload them manually, or track jobs in other systems. The Action handles the full process. Actions are configurable and repeatable, making them suitable for high‑volume production. Each Action can use its own export recipe to control output format, file type, and destination before images are sent to the connected service. 

Who Actions are for?

Actions are designed for everyone involved in studio production, from setup to delivery. They are configured centrally by studio leaders, while photographers, digitechs, and retouchers use them daily without needing to understand how they are set up.

• Studio leaders define how services are connected and how outputs are standardized across the studio. This ensures consistent workflows and predictable results, while keeping configuration and governance in one place.
• Photographers and digitechs apply Actions directly inside Capture One during or after capture. They focus on evaluating results and making creative or technical decisions, rather than managing exports or external tools.
• Retouchers receive cleaner, well-defined inputs that already follow agreed specifications. This reduces clarification cycles, limits rework, and helps production move forward more smoothly.

How do Actions work?

Actions are configured through a web‑based platform used by studio leaders and IT. This browser‑based interface allows leaders to configure connectors, build Actions, and deploy them centrally across the studio. 

Studio for Enterprise & Studio for Teams users can access Actions directly in Capture One as part of their production workflow. To access them, open the Actions tool, click the three dots menu, and select Manage Actions. This opens the interface where available Actions can be viewed and configured.



Studio for Enterprise users can access Actions through the web-based admin portal. 

Behind the scenes, Actions use Connectors to communicate with external services. Connectors are approved links to partner platforms and can be reused by multiple Actions. This keeps integrations controlled and predictable, while Actions remain simple to use inside Capture One.

Supported services

Actions connect Capture One to external services through approved integrations, allowing teams to trigger different types of processing without changing how they work. We’ll keep enabling Connectors to more services, so Actions can adapt to your studio’s production stack.

Pixelz
Retouching for workflows that require review, grouping, and precision edits.

Photoroom
Predefined AI image processing for background removal, layout changes, and product staging.

Gemini
Flexible generative workflows for creative variations, background changes, and composites using prompts.

Next steps