Integration directory

Google Forms × Slack — routing rules

The conditional-routing layer of the integration. IF-THEN rules with 10 operators, per-rule destinations, per-rule templates, and a simulator for debugging without submitting forms.

Start free →

10 operators (equals, contains, gt/lt, is empty, …)
Per-rule destination + template
Simulator, debug rules without real submissions

Spec

The routing layer at a glance

Google FormsSlackIntegration

Trigger

New form submission, after field extraction and normalisation.

Action

Evaluate rules top-to-bottom; first match (or all matches, if fan-out mode) fires.

Fields available

All form fields available as left-hand side; values literal, numeric, or boolean.

Operators

The full operator set

Every operator below is available on every paid plan. No Professional-tier gate; no per-operator pricing. The set is deliberately small, enough to express every routing pattern we've seen in practice, without the maintenance cliff of regex or arbitrary expressions.

equals / not equals: exact string match. Case-insensitive.
contains / does not contain: substring match. The workhorse operator for dropdown text-matching.
greater than, ≥, less than, ≤: numeric. Currency-symbol and comma tolerant.
is empty / is not empty: presence check. Useful for optional fields that signal a higher-priority path when filled.

Patterns

Common rule shapes

1
Route by dropdown
Role contains "Engineering" → #hiring-eng. The dropdown-to-channel pattern. Most forms ship one of these on day one.
2
Route by budget tier
Budget greater than 5000 → #hot-leads; fallback → #new-leads. Numeric routing on a free-text budget field.
3
Fan-out for enterprise
Two rules: Company size contains "500+" → #sales-enterprise AND = "500+" → #vp-direct. Fan-out mode on; both fire.
4
Triage by urgency keyword
Description contains "urgent" → #on-call. Keyword routing for support inboxes.

Quick facts

Limits and behaviour

Rules per form (Solo): 10
Rules per form (Agency): Unlimited
Match mode: First match OR all matches (per form)
Operators: 10, no regex, no boolean nesting
Numeric parsing: Currency + comma tolerant
Per-rule template: Yes, overrides form default

FAQ

Frequently asked questions

What are the available routing operators?▾

Ten operators: equals, not equals, contains, does not contain, greater than, greater than or equal, less than, less than or equal, is empty, is not empty. String operators are case-insensitive by default; numeric operators tolerate currency symbols ($1,200 reads as 1200) and thousands separators. No regex (intentional, almost every regex-rule we've seen is better expressed as contains + a second rule).

How is rule order resolved?▾

Rules are evaluated top-to-bottom. The first matching rule wins by default. You can switch a form's mode to 'all matching rules fire' for fan-out, useful when one submission should land in multiple channels (e.g. an enterprise lead going to both #sales and #vp-direct). The mode is per-form; rule order is enforced via drag-handle in the dashboard.

Can rules combine conditions with AND / OR?▾

Yes, multiple conditions in one rule are AND-joined. For OR, write a second rule with the alternative condition pointing at the same destination. We deliberately don't expose nested boolean expressions; in practice they make rules hard to debug and the two-rules pattern reads cleaner.

What happens if no rule matches?▾

The form's default destination receives the submission (the webhook configured at the form level). If you don't want a fallback, set the default to 'discard' on the form's settings, submissions with no rule match are then logged but not posted to Slack. Useful for forms where 'doesn't match anything we care about' is itself a signal.

Can I test rules without submitting a real form?▾

Yes, the routing rule simulator (linked below) takes your current rules and a sample payload, then walks through which rule fires and why. Faster than submitting variations of the form. Also useful when adding a new rule to an existing form: simulate against the last 10 real submissions before saving to make sure the new rule doesn't poach traffic from existing rules.