You'll be able to nest one condition inside another in Workspace Studio, and a flow will be able to search Drive for a Doc while it runs. The steps start rolling out on Oct 13 for Rapid Release and Scheduled Release domains, and they can take up to 15 days to appear (Google).
The new steps are on by default in the flow builder for Google Workspace customers and Workspace Individual subscribers who already have Workspace Studio. You'll find them in the builder you already use. Admins keep the Studio controls already set for the domain or an organizational unit, and a group that doesn't have Studio doesn't gain it from this release. Both release tracks start together, and then a given account can lag. A teammate can have the steps while yours are still on the way, so open the builder before you rewrite a live flow.
Read this one if a Gmail thread already starts a flow for you, or if that flow opens a Doc from an ID you pasted in. Those are the setups the new steps change. A flow you edit on the first day can still behave differently on a colleague's account while the window is open. If you don't run thread or Doc flows, the steps can wait until a branch of yours needs a second question.
Nested conditions let one branch sit inside another, so a second question can live on a path you already run. Search for a Doc looks up a Drive file from search terms while the flow runs, which is how you reach a contract, brief, or notes doc that changes from one run to the next. Skip Replies, on a Gmail thread trigger, fires the flow on the first inbound message and leaves later replies in that thread alone.
If the builder still looks the way it did last week, the rollout hasn't reached you yet. Turn Skip Replies on before those steps reach a domain where your thread flows are live. Leave it off and a flow that files an attachment or drafts an answer runs again on every reply. Replace hardcoded Doc IDs with the search step once you can see it in the builder. Try the nested path on a message you can afford to have the flow touch, because a condition that looks right in the editor can still grab the wrong mail.
Photo: Aleks Dorohovich / Wikimedia Commons, CC0.
