Free Google Forms → Slack routing rule simulator
Paste a sample submission, set up a few IF-THEN rules, and see which one would fire. Useful for testing rule ordering before you wire anything to Slack.
A JSON object, keys are your Google Form question titles, values are the answers.
Rules run top-to-bottom. First match wins.
Rule #1 (High budget lead) fires → send to #hot-leads
Three pieces: a sample submission, an ordered list of rules, and a fallback
- The sample submission is a JSON object, keys are your Google Form question titles, values are the answers a respondent would have given.
- Each rule names a field, picks an operator (equals, contains, greater than, etc.), provides a comparison value, and a destination channel label like
#hot-leads. - The fallback defaulthandles anything no rule matches, equivalent to the form's default Slack channel in RouteForms.
The simulator walks the rules top-to-bottom for each evaluation. The first rule that matches wins, and we don't evaluate any rule below it. To change priority, reorder rules with the arrows.
Frequently asked questions
What does the simulator do?▾
It evaluates a set of IF-THEN routing rules against a sample submission and tells you which rule would fire (or that none would and the fallback default kicks in). Useful for testing rule ordering before you put them into production.
Does this send messages to Slack?▾
No. The simulator runs entirely in your browser, nothing is sent to Slack, to RouteForms, or anywhere else. The sample JSON and rules never leave your machine.
What operators does the simulator support?▾
All ten that RouteForms supports in production: 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 — '₹50,000' and '50k USD' both compare as 50000.
What order do rules run in?▾
Top to bottom. The first rule that matches wins, and we stop evaluating. Use the up/down arrows next to each rule to reorder, the most specific rules should sit at the top so they fire before any catch-all rule below them.
What if no rule matches?▾
The submission falls through to the default destination, what you typed in the 'Default destination' field. In production this is the form's default Slack channel; if you haven't set one there either, RouteForms records the response as SKIPPED so you can review it.
How is field matching done?▾
Case-insensitive, with leading/trailing whitespace ignored on the field name. So 'Budget' will match a JSON key of 'budget', ' Budget ', or 'BUDGET'. Inside the value, comparisons are also case-insensitive and trimmed.
How do I use this with my real rules in RouteForms?▾
Inside the RouteForms dashboard, every form's Routing rules tab includes a live simulator that pre-fills itself with the fields from your most recent real submission. This standalone tool is for prototyping rules before you've created an account, or for showing a colleague what routing would look like.
Make these rules real
Sign up for RouteForms, paste these rules into a form's Routing rules tab, and route real Google Form responses to the right Slack channel.
Keep reading
How RouteForms's rule engine works in production, operators, ordering, fallback behaviour.
Concrete rule recipes for dropdowns, scales, free text, file uploads, and currency answers.
Once you've designed your rules, here's the script that delivers responses to RouteForms (or anywhere else).
Other utilities for people building Google Forms ↔ Slack pipelines.
All the real options for this hop. RouteForms, SlackQ, Form Director, Zapier, Make, Apps Script, raw webhooks, ranked by fit.