Google Workspace Studio adds branching and document search

Google has announced four additions to Google Workspace Studio: nested conditionals, an option to skip replies in Gmail triggers, more Google Meet calendar outputs, and a step that searches for Docs in Google Drive. Google says these give people more control over workflows built without writing code.

The timing matters if you are planning a workflow now. Google says the rollout is scheduled to start on 13 October 2026 for both Rapid Release and Scheduled Release domains, with feature visibility taking up to 15 days. The features are on by default for end users, subject to their organisation’s Workspace Studio policies. Google lists them as available to Workspace customers and Workspace Individual subscribers who have access to Studio.

Where a small team could use the new steps

For a business of five to fifty people, the useful change is the ability to make a flow respond to more than one situation. Google says nested conditionals let a flow follow multiple layers of decisions. You could use that structure to plan different handling for different types of incoming enquiry, then check each path before relying on it. Google’s announcement describes the capability, not a ready-made enquiry workflow.

Google’s Gmail option lets a thread trigger ignore follow-up replies, so a flow can run on the primary incoming email without running again for every reply. That could make an email-based process easier to manage when a conversation continues. You would still need to decide which incoming messages should start the flow and what action each flow should take.

The new Drive step searches for relevant document files using search parameters, according to Google. That gives a flow a way to look up a Doc while it runs. For example, a team could explore whether a follow-up process can find the document it needs, rather than selecting one fixed file when building the flow. Test the search terms against the documents your team actually uses.

Google also says its Meet step can now output more Calendar event information, including the full invitee list, and supports templates for post-meeting follow-up email drafts. The word drafts matters: Google describes help with preparing follow-up communication, not an automatic decision to send it. A person can review a draft before it goes out.

Pick one flow and check it end to end

Start with a repetitive task your team can describe in a few steps, such as sorting an incoming enquiry or preparing a meeting follow-up. Write down what starts it, where a decision is needed, which Doc a search should find, and who checks the result. These are design choices for your team; Google has not prescribed a particular business process.

• Check access: Google says the additions are for customers and Individual subscribers with Workspace Studio access. An administrator can check the organisation’s domain and organisational unit policies.
• Build a small example: Try one decision path, one document search or one meeting draft before adding more steps. Check what happens when an email receives a reply or a search finds an unexpected Doc.
• Review the output: Decide who should check meeting drafts and whether a flow should use invitee details. Apply your existing review process before using the result in day-to-day work.

If the steps are not visible immediately after rollout begins, Google’s stated rollout window is up to 15 days. Use that time to map the task and its exceptions. A useful first flow is one your team can explain, test and correct when the input changes.