Workspace Studio flows can now branch inside branches and ignore the "thanks!" replies
By Brett Gavaghan, Founder of Adaptd ·
Google is adding nested conditions, a Gmail option to skip replies, richer Meet outputs and a Drive search step to Workspace Studio. The rollout starts on 13 October.
The short version
- Workspace Studio, Google's no-code automation tool, is getting nested conditions, a skip-replies Gmail trigger, more Meet outputs and a Drive search step.
- Google announced it on 9 October 2026; it rolls out from 13 October to all Workspace customers and Workspace Individual subscribers with Studio.
- If you have a Studio flow that fires on every reply or picks the wrong file, revisit it once the new steps appear.
Anyone who has built an email automation knows the moment it fires again because someone replied "thanks!". Google's latest Workspace Studio update deals with that, and adds a few steps that make flows less fragile.
What changed in Workspace Studio?
Workspace Studio is getting four additions that let flows make more detailed decisions and find files on their own. Google announced them on 9 October.
Nested conditionals let you put a condition inside another condition, so a flow can ask a second question after the first, without building a separate flow for each case. A new Gmail setting lets a thread trigger skip replies, so the flow runs on the first message only. The Google Meet step can now pass on more Calendar details, including the full invitee list, and use a template to draft a follow-up email after the meeting. And a new Drive step searches for documents that match what you set, rather than needing a fixed file.
Who gets it, and when?
The new steps reach all Google Workspace customers and Workspace Individual subscribers who have Workspace Studio, rolling out gradually over up to 15 days from 13 October 2026.
They're on by default, so there's nothing for an admin to switch on.
Should your business use it?
Businesses already running Workspace Studio flows should check whether any of them would work better with the new steps, starting with anything triggered by email.
My take: the skip-replies option is the one I'd use first. A flow that logs every new enquiry is useful; one that logs every "cheers, got it" is a spreadsheet with a hobby. The Meet follow-up template is worth a test too, as long as a human reads the draft before it goes. Nested conditions are handy, but resist building a flow so clever nobody else can fix it.
Wondering what this means for your business?
That's exactly what the discovery call is for.