July 2026 release notes for Studio Web in Automation Cloud.

Two new native API workflow activities are now available, Base64 to File and File to Base64. The activities enable you to handle Base64-encoded file payloads without writing custom JavaScript code. You can use them when a step sends or receives a file as an inline Base64 string, for example image or audio data returned inline by an AI model. For more information, see Base64 to File and File to Base64.

Switching to a tracked remote branch no longer risks silently discarding your work. Studio Web now checks whether your local branch has diverged from the remote before switching: safe switches happen immediately, and a confirmation dialog appears only when the switch would discard unpushed local commits or uncommitted changes. For more information, see Version control for solutions.

You can now use templates to create solutions in the Local Workspace. For more information, see Solutions in the local workspace.

Two new project types for business orchestration are now available in Studio Web.

Maestro Case (available since June 12, 2026) introduces a Maestro Case plan designer for goal-driven, exception-heavy processes where the next step is determined at runtime. Use it to model stages, tasks, rules, and SLAs for long-running work such as insurance claims, dispute resolution, or loan underwriting. For more information, see the Maestro Case release notes and the Studio Web Maestro Case documentation.

Maestro Flow (available in Preview since July 7, 2026) is a visual node-based Maestro Flow canvas for building lightweight process orchestrations that connect APIs, AI agents, human approvals, and enterprise services on the Maestro runtime. For more information, see the Maestro Flow release notes and the Studio Web Flow documentation.

We added a Remove unused packages action to the right-click context menu for both projects and solutions. The action identifies dependencies that aren't referenced anywhere in the project or solution and removes them. Before removal, Studio Web takes a snapshot of the solution, so you can roll back the operation if needed.

When you clone an empty Git repository to start a new project, Studio Web now prompts you to add a project. Previously, cloning a repository with no valid project file left Studio Web unable to load.

Studio Web refines the resource mismatch hint introduced in June, which warns you when a bound resource has a different definition available at debug time than at design time. The improvements make drift easier to notice and let you re-sync a resource definition at any time: