What actually changes
At I/O 2025, Google introduced Workspace Flows as a restricted alpha: a utility for building automations across Gmail, Drive and Calendar without writing code. At I/O 2026 the product is renamed Workspace Studio, exits beta and is generally available across all Business and Enterprise plans. That means the feature is included in the subscription, with no paid add-on required for core functionality.
The authoring mechanic remains linguistic: the user describes in any language Gemini supports what they want to automate, and Gemini 3 translates the description into a graph of steps invoking other Workspace apps and external connectors. The I/O demo showed: when an email arrives from client X with a PDF attachment, save it to a dedicated Drive folder, extract the invoice total and update it in the tracking Sheet. Flow generation completes in seconds; the user can edit nodes manually before activating.
What it adds over Flows
Three things, stated on stage and in post-keynote materials.
First is integration with Gemini Spark's agentic layer: Studio flows can invoke Spark for steps that require autonomous reasoning (classify a request, pick the right reply template, decide whether to escalate). This turns flows from deterministic automations into hybrid deterministic+agentic pipelines.
Second is the company-wide template library: an IT admin can publish standard flows (employee onboarding, support-ticket handling, sign-off collection) that other employees see directly in their own Studio interface. This is how Google attempts to turn the tool from an individual gadget into organisational infrastructure.
Third is telemetry. Studio ships a dashboard showing how many flows run, how many errors they produce, how much time they save. For IT admins this is the first step toward governance of automations built by end users — a problem low-code platforms only discovered after broad rollout.
Positioning
Workspace Studio enters a crowded market. On one side, Zapier, Make and n8n have built their advantage on connector breadth. On the other side, Microsoft Power Automate has native Microsoft 365 integration. Studio is not the most powerful of the three — but it is the one that lives inside the inbox and the drive Workspace users already work in.
Google's bet is precise: for 70% of real-world automations (the trivial, recurring, individual ones), convenience beats completeness. You don't need a tool that integrates 6,000 apps; you need a tool that integrates the three apps you use every day and doesn't require opening a separate platform.
What it means for Italian customers
Activation is automatic for all Workspace Business and Enterprise tenants. Italian customers who tried Flows in alpha will see the transition server-side with no manual migration. Compliance data stays in the region chosen by the tenant — a point European customers raised during the alpha phase.
It remains to be seen how Studio will coexist with existing Apps Script flows: Google confirmed the two technologies will live side by side, with Studio aimed at the business user and Apps Script remaining the developer choice. A small ambiguity about the boundary between the two tools.