Conditional routing

Send Google Forms responses to the right Slack channel, based on the answer

Don't pile every response into one #leads channel. Define IF-THEN rules in the RouteForms dashboard and route each submission to the team that should actually see it.

Start free →See an example

10 operators including numeric and contains
Live rule simulator before you go live
First match wins, predictable routing

The model

One rule per row, evaluated top to bottom

Routing rules are spreadsheet-simple, anyone on your team can read them and predict what will happen.

A routing rule has four pieces:

Field name: the exact label of the question in your Google Form (e.g. Budget, City, Property Type).
Operator: how to compare. RouteForms supports equals, does not equal, contains, does not contain, greater than, greater than or equal, less than, less than or equal, is empty, is not empty.
Value: what to compare against. Numeric operators strip currency symbols and commas, so 50000 matches against ₹50,000 or 50k usd.
Destination: a Slack incoming-webhook URL plus an optional channel label you choose for your own bookkeeping (e.g. #hot-leads).

For each submission RouteForms walks the rules from top to bottom and posts to the first match. If nothing matches, it falls through to the form's default Slack destination. There's no implicit fan-out and no rules engine surprises.

Examples

Real routing rules from real RouteForms accounts

These are the rule shapes our customers set up most often. All of them work in two minutes of clicking in the dashboard, no code.

Property Enquiry Form

High-budget real-estate lead

#1IFBudgetgreater than or equal50000→ send to#hot-leads

#2IFProperty TypecontainsCommercial→ send to#commercial-desk

#3IFCityequalsAustin→ send to#austin-team

Bootcamp Sign-up

Course enquiry funnel

#1IFCoursecontainsData Science→ send to#counselor-ds

#2IFCoursecontainsFull Stack→ send to#counselor-fs

#3IFBudgetis empty→ send to#follow-up-needed

Bug Report Form

Customer support triage

#1IFPrioritycontainsUrgent→ send to#oncall

#2IFPlanequalsEnterprise→ send to#cs-enterprise

#3IFAttachment URLis not empty→ send to#bugs-with-repro

Setup

From zero rules to live routing in 90 seconds

1
Connect your form to a default Slack channel first
Set up the form's default Slack webhook on the Slack tab. Every response goes here when no rule matches, make sure the channel exists.
2
Open the Routing rules tab
Only available on Solo and Agency. Click Add rule, pick a field name from your form, pick an operator, type a value, paste the Slack webhook for the destination channel and a friendly label for it.
3
Run the rule simulator
The simulator at the bottom of the tab is pre-filled with the fields from your latest real submission. Tweak the JSON, click Run test, and see exactly which rule (or fallback) would fire.
4
Reorder if needed
First match wins, so place the most specific rules first. Move rules up and down with the arrows on each row.
5
Watch the delivery logs
The Delivery logs tab shows every Slack post with the matched rule, the destination, and the HTTP response from Slack. Filter to Failed to see anything to retry.

Operator cheatsheet

What each operator does

equals / does not equal: case-insensitive, leading/trailing spaces ignored. Best for picklists.
contains / does not contain: case-insensitive substring match. Best for free-text answers ("Tell us about your project").
greater than / greater than or equal: numeric. Strips currency symbols, commas, and trailing units; so 50000 compares correctly against ₹50,000 and 50k usd.
less than / less than or equal: numeric, same normalisation. Useful for routing low-rating feedback to support.
is empty / is not empty: no value field. Catches respondents who skipped an optional question.

FAQ

Frequently asked questions

Can Google Forms route responses to different Slack channels?▾

Not on its own. Google Forms can email a single recipient on submit, but it has no concept of conditional Slack routing. RouteForms adds that layer: rules you define in a dashboard, evaluated for every submission before the message is posted.

How does RouteForms decide which channel to use?▾

Each routing rule names a form field, an operator (equals, contains, greater than, less than, etc.), and a value. Rules run top-to-bottom for every submission. The first rule that matches picks the channel, and we send the message to that rule's Slack webhook. If no rule matches, the form's default Slack channel handles it.

What operators are supported?▾

equals, does not equal, contains, does not contain, greater than, greater than or equal, less than, less than or equal, is empty, is not empty. Numeric operators tolerate currency symbols and commas so '₹50,000' compared against 50000 works.

Can I send to multiple Slack channels for one submission?▾

No. Only the first matching rule fires, by design, that keeps Slack noise down and makes routing predictable. If you really need a response in two channels, point two webhooks at the same form (one rule each).

Can I test a rule before going live?▾

Yes. The Routing rules tab includes a rule simulator: paste a sample submission as JSON, click Run, and you'll see which rule (and which channel) would have matched. The simulator can pre-fill itself with the fields from your most recent real submission.

What happens when I add or reorder rules?▾

New rules can be added without disrupting existing ones. You can reorder rules from the dashboard with up/down arrows, order matters because the first matching rule wins. Disable a rule with the toggle without deleting it.

Do routing rules count against my plan limit?▾

Solo allows 10 rules per form. Agency allows unlimited rules. The Free plan has 0 routing rules, every response goes to the default Slack channel.

Can a rule send to a different Slack workspace than the default?▾

Yes. Each rule has its own Slack webhook URL, so a single form can fan out across multiple workspaces. Useful for agencies routing one client's form into the client's own Slack.