Workflow recipe

Send Google Forms contact form submissions to Slack

The simplest setup: a website contact form, every submission lands in Slack within seconds. Subject-based routing if you need it. No inbox-rot, no “we never saw your message”.

Start free →

Instant Slack notification per submission
Optional subject-based routing (sales / support / partnership)
Free plan covers 30 messages/month

TL;DR

The five-line summary

Build a 4-field contact form (Name, Email, Subject, Message).
Embed it on your site or link to the Google Forms URL.
Install RouteForms; paste the Slack webhook URL.
Optional: add subject-based routing (IF Subject = "Sales" → #sales).
Test with a real submission; verify the message arrives.

Example

What the Slack message looks like

:incoming_envelope: *Contact form. Sales*
<@U01ABCXYZ> please follow up

*Jane Doe* · jane@acme.com
*Subject:* Sales

> Hi, we're a 50-person team evaluating your product for our sales org.
> Could we get a demo next week?

_Submitted via website contact form._

Header: form name + subject tag. Mention the on-duty rep. Name + email on one line for fast triage. Message body in a quote block, readable, not a wall of metadata.

Setup

From blank form to live in 5 minutes

1
Build the contact form in Google Forms
Four required questions: Name, Email, Subject (dropdown with Sales / Support / Partnership / Other), Message (paragraph). Phone optional. Skip company-size and budget questions, those belong in the sales follow-up, not the contact form.
2
Embed or link the form on your site
Google Forms gives you an iframe embed (Send → Embed) or a direct URL. For static sites, iframe is the simplest path; for SPA frameworks where the iframe doesn't fit visually, a 'Contact us' button linking to the Forms URL works just as well.
3
Sign up for RouteForms and add the form
Free plan covers 30 messages/month. Paste the Google Form's edit URL; RouteForms generates a form-specific Apps Script with a unique inbound webhook.
4
Paste the Slack webhook URL
Create an incoming webhook bound to your #website-contactchannel (or whichever you want as the default). Paste it into the form's settings tab in the RouteForms dashboard.
5
Optional: add subject-based routing
One rule per subject. IF Subject = "Sales" → #sales; IF Subject = "Support" → #support. Anything that doesn't match falls to the default #website-contact channel.
6
Install the Apps Script and test
Three-step install per the standard guide. Submit a real form response; the Slack channel should show the message within 5 seconds.

Why Slack beats email for contact forms

The inbox-rot problem

A typical contact form posts to a shared email like hello@example.com or contact@example.com. Three people have access; nobody owns it. Messages sit for 4–48 hours before someone reads them, longer if it's a weekend or holiday. The team learns about a $50K sales enquiry on Monday morning when the prospect has already booked a competitor demo.

Slack creates ownership. Routing the contact form to #website-contactwith a rep mention means somebody's name is on the message within seconds. The shared inbox failure mode goes away.
The team sees response time. A message in a channel sits visibly; a message in an inbox sits invisibly. Channel visibility creates social pressure to respond. Inbox invisibility creates the opposite.
Subject-based routing eliminates triage. Even a 4-field contact form benefits from routing, sales enquiries and support questions need different humans, and the form already asks which one it is.

FAQ

Frequently asked questions

What fields does a contact form actually need?▾

Four for most teams: Name, Email, Subject (or Reason, dropdown of 3-5 common topics), and Message (free-text). Phone number optional. The mistake is asking for company size, role, budget, and timeline on the contact form, those are sales-qualification questions, not contact-form questions. Treat the contact form as the open door; qualify in the follow-up email.

Should I use a Google Form or build a custom contact form on my site?▾

Google Forms is the right call when you want zero maintenance and don't need pixel-perfect branding. The form lives at forms.google.com, you embed it via iframe (or link out), responses arrive in a Google Sheet you control. Build a custom one when (1) the form is brand-critical on a polished marketing page, (2) you need conditional logic Google Forms doesn't support, or (3) you want to capture submissions without redirecting users away. For most early-stage and indie sites, Google Forms is the right default.

How do I route by 'Subject' or 'Reason' field?▾

Add a dropdown to the form: 'Sales / Support / Partnership / Press / Other'. Then one rule per subject: 'IF Subject = "Sales" → #sales', 'IF Subject = "Support" → #support', etc. The default destination catches anything that doesn't match (including 'Other'). Three to five subjects is the sweet spot, fewer feels limiting, more feels like a survey.

Will spam land in Slack too?▾

Google Forms has built-in reCAPTCHA protection, which catches most bot spam. For human spam (one-off random messages), the answer is acceptance, every contact form gets some, and reviewing it takes 2 seconds. RouteForms doesn't have spam filtering of its own; we deliver what the form receives. If spam volume becomes operationally annoying, add a 'how did you find us?' required field, bots tend to leave it blank or paste gibberish, which gives you a routing-rule filter.

Should I auto-reply to the submitter from Slack?▾

Not from Slack directly. Use Google Forms's built-in 'send a copy of responses to respondents' feature for the immediate acknowledgement, and let your team craft the personal reply from email. Slack is for internal notification, the routing alert that says 'someone wrote in'. The auto-reply is a separate concern handled by Google Forms or your CRM.

How fast does the contact form notification reach Slack?▾

Within 1–3 seconds of submission. The Apps Script trigger fires synchronously, RouteForms POSTs to Slack, and the channel sees the message before the submitter even closes the form tab. For contact forms, the speed isn't usually about conversion, it's about not letting messages rot in an inbox.

Can the contact form post to multiple Slack channels at once?▾

Yes, via fan-out mode. Common pattern: post every contact-form submission to a general '#website-contact' channel for the audit trail, AND post sales-tagged ones to '#sales' (or support-tagged to '#support') for the action. RouteForms's fan-out mode fires every matching rule, so one submission can land in two channels with the same or different templates per rule.

What about contact forms that ask for files (attachments)?▾

Google Forms supports file uploads; they go to Google Drive and the submission gets a link. RouteForms includes that link in the rendered Slack message, recipients click through to view the file. The link is permissioned by the form's Drive settings, so if the form is set to 'anyone with the link', anyone in Slack can open it; if it's restricted, only the form owner can.