Forty CI Emails a Day, One Real Failure. Let Gemini Decide Before It Pings You.

At a glance

• A Workspace Studio flow can read each CI alert email, ask Gemini whether it needs you, and ping you in Google Chat only when the answer is true.
• Start with the When I get an email starter filtered to your CI sender, then add a Decide step. Studio pairs it with a Check if step automatically.
• Put Notify me in Chat inside the Check if substeps, and test run the flow before you turn it on.

Your CI sends forty emails a day. Most are reruns and green retries, so the one failing deploy on main sits unread.

Why it matters

A Gmail filter can only match words. Help says the Decide step uses Gemini to analyze content and make a simple true or false decision, so it can separate a failing deploy from a passing rerun even when both subjects say "Build failed." Decide always comes paired with a Check if step prefilled to check for true, and the steps inside run only on a match.

On Friday 9 October 2026, Workspace Updates announced a Studio release with nested conditionals and an option for Gmail thread triggers to ignore follow-up replies. The post says rollout to Rapid Release and Scheduled Release domains starts today, Tuesday 13 October, can take up to 15 days, and is on by default. The how-to below needs neither.

How to triage alert emails with a Decide step

1. On your computer, go to studio.workspace.google.com and click New flow.
2. Click the starter and choose When I get an email. To limit it to alerts, set the From condition to your CI sender, for example builds@ci.example.com.
3. Click Choose a step and add Decide. Studio adds a Check if step with it.
4. In Decide, describe the condition. Click + Variables and insert the email's message body so Gemini reads the actual alert. The block below is our example description, not text from Google.
5. Inside the Check if substeps, add Notify me in Chat and write a short message. Add the subject variable so you can see which alert fired.
6. Click the pencil at the top to name the flow, click Test run and then Start, and wait for "Run Completed." Button names may differ during rollout.
7. Click Turn on.

Decide whether this CI email needs a human today. Answer true if a build or deploy failed on the main branch, a release job failed, or the email says a rollback or outage happened. Answer false if it reports a passing run, a successful retry, a flaky test that passed on rerun, or a failure on a feature branch. Email body: [Message body]

The bracketed text is our stand-in; we haven't verified the chip's name. Replace it with the message body chip from + Variables, since typed words don't link the variable.

Gotchas

• Nested conditionals conflict: Today, 13 October, the Help page still says a flow can't nest conditional steps. The 9 October Workspace Updates post says nested conditionals start rolling out today, over up to 15 days. Until your domain has them, chain separate Check if steps, which Help says run in order.
• Skipping replies: the post's option to ignore follow-up replies has no documented label in Help yet, so we don't name it.
• Gemini access: Help says Decide is only available if you have access to Gemini.
• Account types: Help says personal accounts get Workspace Studio only through Google Workspace Experiments, and some starters and steps are limited to work or school accounts.
• Labels: the email starter filters only on default Gmail labels, not custom ones or searches like label:finance.
• Who gets pinged: Notify me in Chat reaches only you, through a Chat app named after the flow. A sender variable shows as plain text, not an @mention.

Recommended AI prompt

Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.