Google announced on 9 October that Workspace Studio is getting four new steps, with a gradual rollout starting on 13 October. Two of them target the problems that appear once a flow is pointed at a real shared inbox: replies setting it off again, and decisions that need more than one yes or no.
If your firm already runs flows on Gmail, check them once the update reaches your domain.
What Google has announced
The October release adds nested conditionals, so one branch of a flow can contain its own branches. It adds a Gmail setting that lets a thread trigger ignore follow-up replies, so the flow runs only on the first incoming email. Meet steps now output more calendar detail, including the full invitee list, with template support for post-meeting follow-up drafts. And there is a Drive step that searches for documents using search parameters.
Rollout is gradual, up to 15 days before the features are visible, starting on 13 October. The features are on by default and follow your existing Workspace Studio domain and organisational unit policies. Google does not say how deep nesting can go, so I would not plan around a specific depth until you have tried it.
Where this bites in a real firm
Take an enquiries inbox. A flow starts when an email arrives, saves the attachments to a Drive folder and drafts a reply. The first message works. Then the customer replies, and that reply is another email for the flow to pick up. Google’s wording suggests the new setting stops this. I have not tested it, because the rollout only starts on 13 October.
Nested conditions are about the same kind of friction. Google’s help guide describes a Check if step that carries on only when your conditions are met, with AND and OR between them. Nesting lets a flow take different routes instead of simply stopping. Supplier invoice or customer order, then over a value or under it, is two decisions, and until now you would have squeezed it into one condition or built two flows.
What to do this week
Open Workspace Studio and list every flow that starts from Gmail. Write down who built each one and what it does when a thread gets a second message. Flows nobody reviews are the same problem I found in my own CRM automations.
Once the update shows up, test with a dummy email and a reply to it, then check the run history for duplicate folders or drafts. Leave the flows that already work alone. The earlier Studio changes are worth a read first if you have not used it yet.
If you want help finding which of your repeat admin jobs are worth automating, the free audit at digilyse.co takes about ten minutes.
Want this kind of analysis monthly?
The Digilyse Brief is a monthly LinkedIn newsletter from Tom Burke covering what works, what doesn’t, and the operational patterns we keep seeing across owner-managed UK firms. No pitching, no hype. Subscribe on LinkedIn.
Published by Digilyse. Practical systems for growing businesses.