Workspace Studio flows just got real automation steps

Workspace Studio, the automation builder tucked inside Google Workspace, just picked up four new action steps: move a Drive file, copy a Drive file, reply to an email thread, and post a Chat reply. Google finished the rollout on September 14, 2026, and it landed on Business Starter, Standard, and Plus, the same plans most small businesses already pay for.

Before this update, a Studio flow was mostly good for one thing: running a prompt through Gemini and posting the result somewhere. It could read and summarize, but it could not close a loop. These four steps change that. A flow can now touch a file directly, finish an email conversation, and notify a Chat space, which covers most of what an internal handoff actually needs.

What actually shipped

• Copy Drive file or folder: duplicates a file or folder when a flow runs, useful for turning a template into a new client folder on demand.
• Move Drive file or folder: relocates files without someone dragging them by hand, so a signed contract can land straight in the right project folder.
• Reply to email: sends a reply inside an existing Gmail thread, so a flow can close out a request without breaking the conversation history.
• Send a Chat reply: posts a formatted reply, including Markdown lists and code blocks, into a specific Chat space or thread.

When Workspace Studio flows can replace a paid Zap

For the narrow case of a workflow that starts and ends entirely inside Google Workspace, Workspace Studio flows now cover ground that used to need a Zapier or Make step just to move a file or send a reply. If client intake runs through a shared Drive folder and a shared inbox, and nothing in that chain lives outside Workspace, some of those paid zaps can retire this quarter.

Where it still falls short

Studio flows reach only as far as Google Workspace apps. There is no step for Stripe, QuickBooks, a CRM, or a booking tool, and this update adds new actions, not new triggers. If a workflow needs to touch anything outside Gmail, Drive, and Chat, it still needs n8n, Zapier, or Make sitting in the middle of it.

1. 1

   Pick one fully internal handoff

   Look for a workflow that never leaves Gmail, Drive, and Chat, like client intake, contract filing, or an internal request queue.

2. 2

   Add the new step to an existing flow

   Open Workspace Studio and drop Move Drive file, Copy Drive file, Reply to email, or Send a Chat reply into the spot where a person currently does that step by hand.

3. 3

   Set the admin guardrails yourself

   If you manage the workspace, decide now which of the four steps should require approval before sharing data outside the organization, rather than leaving the default in place.

4. 4

   Leave the cross-tool zaps alone

   Do not migrate anything that touches a tool outside Workspace. Those workflows still need a real automation platform behind them.

If you are not sure which of your Zapier or Make workflows are pure Workspace-to-Workspace and which ones lean on outside tools, that split is worth mapping out before you move any pieces around, and it is the kind of thing a second pair of eyes catches fast.