Free Google Forms field extractor for routing rules
Paste a response. Get the exact field names, detected types, and ready-to-paste routing rule snippets. The fastest way to find the strings your IF-THEN rules need to match.
We'll list the exact field names so you can paste them into a routing rule.
Use these strings verbatim in your routing rules.
Full nametextSample: Priya Mehta
EmailemailSample: priya@example.com
Domain matching:
IF Email contains "@yourcompany.com" → #internalBudget (USD)currencySample: $50,000
Numeric routing:
IF Budget (USD) >= 50000 → #hot-leadsCitytextSample: Bangalore
Geo routing:
IF City = "Bangalore" → #blr-teamInterested inmultiSample: SEO, Slack
Multi-select match:
IF Interested in contains "Slack" → #slack-teamNewsletter opt-inbooleanSample: Yes
Boolean branch:
IF Newsletter opt-in = "Yes" → #subscribedSubmitted atdateSample: 2026-05-30T10:14:00Z
Drop these straight into your form's Routing rules tab.
Domain matching: IF Email contains "@yourcompany.com" → #internal
Numeric routing: IF Budget (USD) >= 50000 → #hot-leads
Geo routing: IF City = "Bangalore" → #blr-team
Multi-select match: IF Interested in contains "Slack" → #slack-team
Boolean branch: IF Newsletter opt-in = "Yes" → #subscribedThe single most common reason routing rules silently fail
A teammate renames a Google Form question from Budget to Budget (USD). The form still works. Submissions still arrive. But every routing rule pointing at Budget stops matching, and nothing visibly breaks, responses just stop landing in the channels they used to. By the time anyone notices, a few leads have slipped through.
The extractor is a 5-second sanity check against that failure mode. Paste your most recent real submission, eyeball the field names against your rules, and confirm the strings line up. If they don't, the suggested snippets give you the corrected rule text to paste back in.
Names, types, and a starting rule per field
- Field name: the exact string the form stores. Copy-paste safe, no normalisation, no trimming visible characters that might actually be part of the question title.
- Detected type: text / email / url / numeric / currency / boolean / date / multi. A hint for which operators make sense (e.g.
>=for currency,containsfor multi-select,equalsfor boolean). - Sample value: the value from the response you pasted, so you can sanity check the type detection matched the data you've actually got.
- Suggested rule: an IF-THEN starting point tailored to the type. Edit the threshold and channel for your workflow.
From sample submission to live routing in three steps
- Get one real submission.Fill the form yourself if you don't have any responses yet. Copy the response JSON from the Apps Script Executions log, or copy the row from the Sheets responses tab.
- Paste it here. The extractor lists every field with the detected type and a suggested rule. Read down the list, decide which fields you want to route on.
- Copy the rule snippets.Paste them into RouteForms's Routing rules tab. Edit thresholds and channel names. Use the routing rule simulator to verify them against the same sample submission before going live.
Frequently asked questions
What does this tool do?▾
It pulls the exact field names out of a Google Form response so you can paste them verbatim into a routing rule. Field names in routing rules have to match the form's question titles exactly, a single character off (a trailing space, a colon, sentence case vs Title Case) and the rule won't match anything. The extractor strips the guesswork.
What input formats does it accept?▾
Three, auto-detected: (1) a JSON object, either flat { 'Name': 'Priya', ... } or the Apps Script onFormSubmit event payload with namedValues; (2) a TSV, two tab-separated lines (headers, values) you'd get from copying a row out of the responses Sheet; (3) plain Name: value or Name = value lines. Anything that doesn't fit gets a warning and is ignored.
How does type detection work?▾
We inspect the sample value with a few regexes, email shape, URL shape, ISO date, currency (₹/$/€/£ prefixes or USD/INR/GBP suffixes), plain numeric, yes/no/true/false, comma-separated multi-select. Plain text falls through to 'text'. Type is a hint for which RouteForms operators make sense for that field, numeric for >=, contains for multi-select, equals for boolean.
What are the suggested rule snippets?▾
For each field, we infer a sensible IF-THEN routing rule based on the detected type. For a currency field called 'Budget', the suggestion is 'IF Budget >= 50000 → #hot-leads'. For an email field, 'IF Email contains "@yourcompany.com" → #internal'. For a multi-select 'Interested in' field, 'IF Interested in contains "Slack" → #slack-team'. They're starting points, edit the threshold and the destination channel to fit your workflow.
Why is the exact field name so important?▾
Inside RouteForms, routing rules match against the form question title as Google Forms stores it. If your question is 'Budget (USD)' but your rule says 'Budget', the rule won't match. The extractor pulls the title verbatim so a copy-paste guarantees the match. (RouteForms's matching is case-insensitive and trims whitespace, but the visible text has to be right.)
Does the tool send anything to RouteForms?▾
No. Everything runs in your browser. Your form data and the inferred field names never leave your machine. The page is fully usable without a RouteForms account.
What if I have duplicate field names?▾
Google Forms allows two questions with the same title, but it breaks routing, both responses land under the same key and you can't target one without the other. If the extractor lists the same name twice, that's a flag to rename one of the questions in the form before going live.
Can I see the field types if I haven't filled the form yet?▾
The detector needs a sample value to infer type. If you only have field names and no responses yet, the extractor still gives you the names, just leaves the type column blank or set to 'text'. Once you have one real submission, paste it in and the types fill themselves.
Wire these field names into real routing
RouteForms takes the rule snippets above and routes every Google Form response to the right Slack channel. Free for 30 responses a month.
Keep reading
Test the rule snippets above against the same sample submission before putting them in production.
If you want the full Slack message instead of just the field list, the formatter renders the message and the Block Kit JSON.
How RouteForms's rule engine works in production, operators, ordering, fallback behaviour.
All the real options for delivering Google Form responses to Slack, ranked by fit.