Google Workspace Studio added logic and search steps. What a small office can now automate without Zapier

What did Google add to Workspace Studio in October 2026?

Google shared four new features on its Workspace Updates blog on 9 October 2026. First, Nested Conditionals lets you place one condition inside another condition. Second, Gmail Skip Replies makes a flow start only on the first email in a thread. Third, Search for a Doc looks up a Google Doc while the flow is running, so you do not have to pick that exact file ahead of time.

The fourth change helps with meetings. The Google Meet step now pulls in more details from your calendar, including the full list of people invited, and it includes a template to draft a follow-up email once the call ends. Back in September, Studio also gained the ability to move and copy Drive files and reply to an email in its thread, and that addition is the main reason Studio is now worth comparing with Zapier.

Google started rolling these features out on 13 October 2026 and gave it up to 15 days, so you should see them in your account by now. If you are on a work account, you need an eligible edition, which includes Business Starter, Standard and Plus as well as Enterprise Standard and Plus, and your admin must turn Gemini on for you. If you are on a personal account, you need Google Workspace Experiments.

I put this article together on 6 November 2026 by reading the official pages from Google and Zapier. I have not built this exact invoice flow inside my own account yet, so whenever a rule comes from a help document rather than my own testing, I will tell you plainly.

Should a small office use Workspace Studio, Zapier or Apps Script?

Right now, most search results for this update just repeat Google’s announcement, so I wrote the direct comparison I wanted to read for myself. In my own work, I usually build jobs like this in Google Apps Script, so I have no reason to push you toward Studio or Zapier. Every price and limit I mention here matches what was published on 6 November 2026.

On Zapier, the free plan only gives you one trigger and one action, which means the invoice flow in the next section will not fit on it. Because of that limit, a fair price check has to compare Zapier Professional against a Google Workspace plan you might already pay for every month. If your office is on Business Starter or higher, testing Studio first only costs you an afternoon of your time.

How do I build a supplier invoice flow in Workspace Studio?

Here is how the invoice job works as a single flow. It begins with the starter When I get an email, filtered so it only watches for emails containing the word invoice. Next, the flow saves the attachment into Drive, and then a Decide step asks Gemini a plain yes or no question: does this email ask for urgent payment?

Whenever you use Decide, it pairs up with a Check if step, which compares two values and only runs its substeps when the rule matches. Substeps are just the smaller actions tucked inside that condition. When the answer comes back true, the flow sends a Chat message to accounts and adds a row to the tracking sheet. Because Studio now supports nesting, you can put a second Check if inside that same branch so it messages the business owner only when the email comes from a key supplier.

If your account only has the plain Check if step because Gemini is not turned on, you will not see the Decide step at all. You can still filter emails by matching exact words in the message, which is less clever than an AI check, but much easier to predict. Because Decide relies on an AI answer, I treat it the same way I treat any figure a software tool gives me, which I wrote about in how to check AI numbers in Excel, and I would check its answers against real emails for the first week before trusting it.

Why can't the main flow use what a branch produced?

Here is the first rule that changes how you lay out your flow. According to Google’s help page, you cannot take variables created inside substeps and use them later in the main flow. A variable is simply a piece of output that an earlier step produces, such as a drafted email reply. In Google’s own example, if a branch asks Gemini to write a reply, you cannot take that drafted text and drop it into a tracking document at the bottom of the main flow.

Because of this rule, the clean habit of branching early and logging once at the very end fails whenever your log needs details created inside a branch. Put the step that adds a row inside every single branch, rather than once at the end of the flow. That is why the add a row step appears twice in the diagram, and it is the first place I would look if your tracking sheet starts showing blank cells.

Studio also has no else branch for when a check fails. If you want the flow to do something when a condition is false, Google says to add another Check if step with the opposite rule. Also, a single Check if step can join rules with AND or with OR, but it cannot mix both in the same step, so a filter like “from Ali or Sara, and marked urgent” requires one condition nested inside another, which this update now allows.

Building this way uses up your step count fast. When I count the starter and every action in the invoice example above, that small job already takes 13 steps. Google’s own documentation disagrees on the maximum allowed, because the limits page lists 100 steps per flow while the admin setup guide says the limit is 20. Build your flows assuming the limit is 20 steps.

What does Skip thread replies miss in Gmail?

The second rule to watch is Skip thread replies, which appears as a simple tick box on the Gmail starter. According to Google’s guide, ticking this box makes the flow run only on the very first email of a new conversation, while ignoring every reply that follows in that thread. For filing incoming invoices, that sounds great, because an email chain with six back and forth messages will not trigger six extra runs and six duplicate rows in your sheet.

In real work, though, suppliers often reply in the same thread. A corrected invoice or an urgent payment chaser often lands inside that original email thread, and if you ticked that box, your flow will completely ignore it. That means the urgent payment check in my earlier example would miss the exact email you built it to catch. Tick the box for the flow that files brand new invoices, but leave it unticked for any flow that watches for payment reminders.

Splitting those jobs into two separate flows also keeps you safer against Google’s run limits. Every time any flow you own runs, it counts toward one shared daily allowance for your account, and Google does not tell you what that number is. If you reach that ceiling, every active flow you own stops working until the daily counter resets, and any runs triggered while it is paused simply fail. You should narrow each starter with a specific sender or subject word, which matches Google’s own advice, and remember that Google’s AI usage limits page lists Studio under promotional access where stricter limits may apply later, so do not build workflows that push your account to its daily edge.

Which file does Search for a Doc pick when several titles match?

The third rule sits inside Search for a Doc, which looks like the easiest new step on the surface. Google’s documentation explains that this step searches by title across Google Docs that you own, and if more than one file matches, it quietly picks whichever file was modified most recently. It makes that choice without asking you, and the rest of your flow keeps running with that file.

You can see how easily this goes wrong in a normal office. Say you make a rough copy of your reply template to test an edit yesterday, and today your live flow can start pulling text from that rough copy because it has the newest timestamp. Also, because the help page specifically says docs you own, a template created by a teammate might not show up in the search at all, even if they shared edit access with you. Finally, the guide only mentions Google Docs, so I would not expect this step to find a PDF or a Google Sheet.

Fixing this takes a simple naming habit. Give your live template a unique title that no other file shares, and wrap that exact title in quotation marks inside the search box. You can use a clear code like "TEMPLATE supplier reply v1", and make sure the file is owned by the exact same Google account that owns the flow. Even with quotation marks, the search can still match a longer file title that contains your phrase, so never leave backup copies with that same code in their names.

What should I check before a flow runs for real?

When you test your setup, keep in mind that a test run takes real actions. It actually sends the chat messages and edits the real files in your Drive, rather than showing you a harmless preview. That detail matters much more now that a Studio flow can reply directly inside an email thread, because a test run can send a real message straight to a supplier.

1. 01
   Point it at yourself first

   Make the email starter match a test subject line only you send, and send the Chat messages to yourself until the answers look right.
2. 02
   Draft, do not send

   Use a draft reply step at the start, so a person reads each one. Move to the Reply to email step only when you have read enough drafts to trust it.
3. 03
   Check the Activity tab daily for a week

   Runs are listed there with their status. A problem shows as a red dot in the Studio icon in Gmail and in the Activity tab, and it is easy to miss if nobody is looking.
4. 04
   Write down who owns it

   Put the owner, the flow name and what it does in one line in your tracker sheet, so the flow is not a mystery when that person is away.

What happens to a Workspace Studio flow when the owner is away or leaves?

Before you build anything for your company, there is one ownership limit you need to weigh carefully, because this is where small teams get stuck. Google states that flows run on behalf of their owner, meaning every message sent and every file touched is recorded under that single person’s name. Sharing a flow with your team does not turn it into a shared team asset either. When you send a sharing link to a coworker, it only lets them make a copy, so they still cannot edit your live flow or check its run logs.

When a coworker makes that copy, it brings over all of your personal settings, including links to your files, your text and your email addresses, so they have to open every step and swap those details out by hand. On personal Google accounts, you cannot even share a flow link at all. I searched Google’s documentation and could not find any guide on how to transfer a working flow to a new owner when a staff member leaves the company, so you should assume you may have to rebuild it, and check with your workspace admin before putting important work on it.

Zapier solves this team problem properly on its paid team tiers, where an admin can hand a departing employee’s Zaps and app connections over to someone else, and everyone on the team can inspect the run logs of shared workflows. The catch is the price, because Zapier’s Team plan costs $69 a month when billed yearly. You have to ask yourself how much damage it would cause if a flow quietly broke for a full week and nobody noticed. For a small helper task, Studio is fine, but for an end of day sales report that your boss reads every evening, I want more than one person in the office able to check that it ran.

If your company runs on Microsoft instead of Google Workspace, you will run into the exact same questions with Power Automate, and I cover that side in refreshing Excel Power Query with Power Automate.