For teams who live in Slack

The Google Forms notification add-on for Slack

Most Google Forms notification add-ons send email. RouteForms ships Slack notifications for Google Forms — every response in the right channel, with routing rules, a delivery log, and automatic retries on failure. Install in two minutes. Free for 30 responses a month.

Start free Generate the Apps Script

Why Slack, not email

The notification add-on most teams actually need

Email notifications were the right answer when one person owned every form response. They're the wrong answer when the response needs the right team to see it within minutes.

Email distribution lists are noisy. Adding a person means a workspace admin task. Removing them is forgotten. Filtering is per-user, never per-team.
Slack channels are cheap. One per workflow: #hot-leads, #support-oncall, #real-estate-luxury. Routing by form answer is a UI checkbox, not a forwarding rule.
Slack is where the response happens. Reactions, mentions, threaded follow-up, file attachments — all built in. Email replies fragment into 12 private threads nobody else can see.
Silent failures are visible. A bounced email disappears. RouteForms logs every Slack response code and retries transient failures automatically.

How it installs

Two minutes from paste to live notifications

The install is shorter than a Workspace Marketplace add-on flow because there's no permission-bundle review — you grant exactly what the script needs and nothing more.

1
Create a free RouteForms account
Sign in with Google. Free plan covers 30 responses a month, one form, one Slack destination — no card needed.
2
Paste your Slack incoming-webhook URL
Add a webhook in your Slack workspace pointing at the channel you want responses in. Paste the https://hooks.slack.com/… URL into RouteForms.
3
Install the Apps Script
Open the form's three-dot menu → Apps Script. Paste the script we generate, save, run installFormBridge once. That creates the onFormSubmit trigger so every future submission lands in Slack automatically.
4
(Optional) Add routing rules
Solo / Agency plans add IF-THEN routing — different answers to different Slack channels. Build the rules in a dashboard, not in code.

vs Email add-ons

A like-for-like comparison

Capability	Typical email add-on	RouteForms (Slack)
Notification destination	Email inbox / distribution list	Slack channel (with routing)
Conditional routing by answer	Add-on specific; often per-recipient filtering	IF-THEN rules in a dashboard, first match wins
Delivery log a non-engineer can read	Usually none — bounces are silent	Per-form log with status, response, retry button
Retry on failure	Manual resend at best	Auto with backoff; alert on streak (paid plans)
Mention / route to on-call	Hard — depends on email distribution rules	<!subteam^…> in the template, set per rule
Free tier	Usually 100 emails / month, with branding	30 responses / month, no branding

For teams that still want email — keep Google Forms' built-in email notifications on. They run in parallel with RouteForms; one for the archive, one for the working surface.

FAQ

Frequently asked questions

What is a Google Forms notification add-on?▾

An add-on (or third-party integration) that sends a notification every time someone submits your Google Form. Most popular add-ons send an email to a list of recipients. RouteForms is the same idea, but the notification lands in a Slack channel instead — with optional routing rules so different responses go to different channels.

How is this different from Google Forms' built-in email notifications?▾

Built-in email notifications only send to the form owner, with no formatting and no routing. Notification add-ons add custom recipients, message templates, and conditional logic. RouteForms goes further: instead of email at all, your team gets the response as a clean Slack message in the right channel — readable inline, mention-able, threadable, and with a delivery log you can audit.

Why Slack instead of email?▾

Three reasons teams switch. (1) Speed: Slack is where decisions get made, email is where decisions go to die. (2) Routing: Slack channels are cheap to create; you can have one per workflow (#hot-leads, #support-oncall, #real-estate-luxury) and route conditionally. Email distribution lists are expensive to maintain. (3) Visibility: a Slack message gets reactions, mentions, and threaded follow-up. An email blast gets ignored.

Is RouteForms a Google Workspace Marketplace add-on?▾

Not in the technical sense. We don't ship as a Workspace-Marketplace listing; we ship as a Google Apps Script you paste into the form once (90 seconds). That's a deliberate choice — it gives you control over the script, avoids Marketplace verification cycles, and means you never have to grant a third-party app workspace-wide access. Functionally it behaves like an add-on: install once, then every submission gets routed to Slack.

Does it work with all Google Form types?▾

Yes — short answer, paragraph, multiple choice, checkboxes, dropdown, linear scale, multiple-choice grid, checkbox grid, file upload, date, time, and quiz responses. Every visible field shows up in the Slack message. Multi-select questions get joined with commas in the default template; you can customise.

How does the install compare to an email add-on?▾

Email add-ons typically need: install add-on → grant permissions → configure recipients → set template → activate. Maybe 5 minutes. RouteForms: paste your Slack webhook URL → paste the Apps Script → run installFormBridge once → done. Maybe 2 minutes. The Apps Script step is what an email add-on would do behind the scenes — we make it visible so you can read every line before granting access.

What happens when Slack rejects a notification?▾

RouteForms retries transient failures (5xx, 429 rate limits) automatically with exponential backoff. Permanent failures (invalid channel, expired webhook) surface in the per-form delivery log with the exact error. On paid plans, a streak of failures triggers an email alert so silent failures don't stay silent. The delivery log shows every attempt, every response code, every retry — a layer email add-ons don't usually surface at all.

Can I have both Slack and email notifications?▾

Yes — keep Google Forms' built-in email notifications on for whoever wants the receipt by email, and use RouteForms for the team's Slack channel. They run in parallel; neither one blocks the other. Most teams keep email for the form owner's archive and use Slack as the working surface.