Google Workspace Studio Flows gets four new automation steps for Drive, Chat, and Gmail

Google Workspace Studio Flows is getting four new automation steps that close some genuinely useful gaps in everyday document and communication workflows. From 8 September 2026, all Workspace domains will have access to Move Drive file or folder, Copy Drive file or folder, and Send a Chat reply. The Reply to email step follows on 14 September 2026.

These are not preview or beta additions. Google is shipping these as production-ready steps you can drop straight into your Flows.

What each new step actually does

Copy Drive file or folder makes a copy of a specified file or folder each time a flow runs. The obvious use case is template generation: set up a flow that copies your standard project brief or onboarding document whenever a trigger fires, rather than doing it by hand every time.

Move Drive file or folder relocates files automatically based on whatever logic you build into your flow. If you run intake processes where documents need to land in a specific folder after review or approval, this removes the manual step of dragging files around Drive.

Reply to email sends a response inside an existing Gmail thread. It preserves the conversation history, which matters for support queues, task-tracking workflows, or anywhere context continuity is important. The automation replies from within the thread rather than starting a new one.

Send a Chat reply posts a message into a specific Google Chat space or thread. Notably, this step now includes Markdown support, so automated messages can use bold text, bullet lists, and code blocks rather than plain text. For teams routing notifications or status updates through Chat, that formatting flexibility makes a real difference to readability.

What this means for you

Until now, Workspace Studio Flows covered a reasonable range of triggers and actions, but gaps in file management and cross-channel replies meant many workflows still needed a manual handoff or a workaround via Apps Script. These four steps fill in those gaps without requiring any code.

A few practical examples of what becomes straightforward to automate:

A new form submission triggers a flow that copies a template folder in Drive, names it after the submitter, and sends a formatted confirmation reply in Chat.
An email arrives in a support inbox, a flow categorises it and sends a Reply to email acknowledging receipt, then moves a related Drive document to an “in progress” folder.
A project hits a milestone (tracked via a Sheets trigger), a flow moves the deliverable to a client-facing Drive folder and posts a Chat reply in the project channel.

None of these required a developer before, but they did require patience or workarounds. Now they are a few steps in Studio Flows.

Who gets access

These steps are available to all Google Workspace customers who already have access to Ask Gemini in Drive, Ask Gemini in Chat, or the Gemini side panel in Gmail, Sheets, or Slides. That covers most Business and Enterprise tiers. Personal Gmail accounts and users under 18 are not eligible.

The rollout is phased:

Drive and Chat steps: Admin controls available from 1 September 2026; features live for end users from 8 September 2026.
Gmail steps: Admin controls available from 8 September 2026; features live for end users from 14 September 2026.

Both Rapid Release and Scheduled Release domains follow the same schedule.

Admin controls worth knowing about

Admins have meaningful controls here. The Send a Chat reply step is on by default if your organisation already permits Gemini for Google Workspace steps, but individual steps can be disabled independently. You can also enforce a policy requiring explicit end-user approval before a flow executes any action that shares data outside the organisation.

Data Loss Prevention rules for Studio also apply here. If your organisation uses DLP to restrict what Gemini can access in Drive, those restrictions carry through to flow execution, including the ability to block or require review before a step runs based on the sensitivity of the data involved.

Usage limits that came into effect on 1 September 2026 are also worth noting: users can have up to 100 flows in total, no more than 25 active flows triggered from Gmail events, and each flow can contain up to 20 steps.

Getting started

You can access Workspace Studio at studio.workspace.google.com or via the side panel shortcut inside Gmail, Drive, or Google Chat. The new steps will appear in the flow builder alongside existing steps once the rollout reaches your domain.

If you have been building workarounds for file management or threaded replies in your existing flows, it is worth revisiting those once the steps are available. In most cases, a native step will be cleaner and more maintainable than the workaround it replaces.