3. Branching

Route incoming Webhook leads into regional Slack channels with a Conditions Step, then merge all four routes into one Google Sheets row.

At a glanceVerified in app · Oct 30, 2026

Use it to: Route Webhook leads across four regional Slack branches with Conditions and merge them into one Google Sheets row in OR mode
Find it: Automations → Create new → Workflow (Tools → Flow → Conditions)
Cost: Free for Webhook and typed Conditions rules · 2 Step credits per test run (1 Slack + 1 Google Sheets)
Output: One regional Slack alert and one appended Google Sheets row per test run
Instead: Switch (/build/action-steps/switch) when matching one field against fixed cases with first-match routing

WebhookConditionsSlack routesGoogle Sheets

Open in Glow ↗Connect AI via MCP ↗

Clones a Draft copy or builds deterministically via Glow MCP (0 Step credits, 0 AI tokens). Nothing runs automatically.

🎯

What you will learn: Drafting branches with the Workflow Assistant, writing mutually exclusive rules, and merging routes in OR mode.

Before you start: Complete Tutorial 2 and connect Slack and Google Sheets. Prepare four test Slack channels, a test sheet (name, email, region), and available Step credits and Glow AI tokens.

Step 1: Build the Branches

Prompt the Assistant

Open Automations → Create new → Workflow, click Assistant at the bottom right, and enter:

“Create a Webhook trigger with name, email and region fields. Add a Conditions Step with three mutually exclusive routes: region equals US East, US West or Europe. Use ELSE for everything else. Connect a separate Slack Send Message Step to each route. Leave the automation in Draft so I can configure accounts, channels and messages.”

Watch it Build

Review Assistant Draft

Answer any setup prompts. Confirm the draft has one Webhook, one Conditions Step, and four Slack Steps wired to the four routes.

Give the Webhook test data

Enable Body only in the Webhook Step so posted fields sit at the top level instead of under body. In Test & Debug → Testing data, click the pencil icon, paste this JSON, and press Cmd+Enter:


{ "name": "Ada Lovelace", "email": "[email protected]", "region": "Europe" }

How a Conditions Step Routes

A Conditions Step checks every named route and fires all matching branches. Unmatched runs take ELSE, so keep region rules mutually exclusive.

A record arrives:

£24,000 · United Kingdom

runsDeal size is over 10,000Notify sales
runsCountry is United KingdomAdd to CRM
skippedELSE — none matchedLog for review

Both conditions are met, so both routes run. This is the part a first-match step cannot do.

Step 2: Set the Rules

Tutorial 3 on the Glow canvas: New Lead Webhook connected to Conditions step, splitting into four Slack channels (US East, US West, Europe, and General Queue), with the Conditions setup drawer open. — The routing portion before the Google Sheets merge is added. Configure three region rules and an ELSE route, each connected to its Slack Step.

Click Conditions and map region from the Webhook data picker for each named route (US East, US West, Europe). ELSE needs no rule.
In each Slack Step, select your connection and test channel, then map name, email, and region from Workflow data.

Step 3: Merge the Branches

Record every lead in one Google Sheet regardless of which regional route ran.

Add Google Sheets

Open Apps in the dock, choose Google Sheets → Add Single Row, and place it to the right of the Slack Steps.

Configure it

Select your Google Sheets connection, test spreadsheet, and worksheet. Map name, email, and region from the Webhook Step.

Merge the Branches

Drag a line from the output terminal of all four Slack Steps into the input terminal of the Google Sheets Step.

Set the merge mode

Click the input terminal on Google Sheets and choose OR (Data from any step). Note that a failed Slack Step stops its branch before reaching Sheets.

Mutually Exclusive BranchesOR (Data from any step)

Runs as soon as one incoming branch finishes.
Use when a record takes only one route, like region routing.

Parallel BranchesAND (Data from all steps)

Waits until every connected incoming branch has finished.
Use when all branches run in parallel and must rejoin.

Step 4: Test the Routes

Draft is not a sandbox: Run sends real messages. Pin write Steps or point all four Slack Steps and Google Sheets at test destinations before clicking Run (How testing works).

Four Region Tests

Keep the automation in Draft and test region set to US East, US West, Europe, and Other. Confirm each run posts one Slack message to the expected channel and adds one row to the sheet.

The tutorial is complete when all four inputs reach their expected channel and each adds one row. If a write is uncertain, check Slack and the sheet before rerunning (Testing & Debugging).

Optional: enable automatic intake

Before switching to Live, complete the Before you turn it on checklist. If you change any destination, test it once in Draft first, then switch to Live and follow Operating Automations.

Verify it works

Run: Keep the automation in Draft and run four tests with region set to US East, US West, Europe, and Other.
You should see: Each run sends one message to the matching Slack test channel and appends one row to the Google Sheet.

What’s Next?

👉 Continue to 4. Your First AI Agent →

Explore Use Cases & Examples.
Building with a teammate? See Working Together.
Read Operating Automations before going live.