Free Google Forms tools
Tools that work with the Google Forms side of the pipeline: pulling field names out of a response, formatting raw data into a Slack-ready message, generating the Apps Script that delivers submissions, and emitting test payloads for downstream endpoints.
Google Forms to Slack Generator
Paste a Slack webhook URL (or any HTTPS endpoint), get a copy-paste Google Apps Script that sends every form response to Slack.
Google Forms Webhook Generator
Paste any HTTPS endpoint and pick a payload shape. Get an Apps Script that POSTs every form response to the URL, with optional bearer auth.
Response Formatter
Paste raw form data. JSON, a Sheets row, or key: value lines. Get a Slack-style preview and a paste-ready Block Kit payload.
Field Extractor
Paste a response. Get the exact field names, detected types, and ready-to-paste routing-rule snippets.
Webhook Payload Generator
Sample webhook JSON in three shapes (flat, Apps Script event, RouteForms-style) plus a copy-paste curl command.
Notification Add-on for Slack
The Slack-vs-email notification add-on positioning page. Install in two minutes, with routing rules, delivery logs, and retries.
Response Notification Generator
Build a notification template: Slack Block Kit + email subject/body + recommended routing rule, side by side, with urgency-aware mentions.
What every form-to-Slack workflow has to handle
A Google Form is the simplest data source in the world, questions go in, answers come out, and you can read them in the responses Sheet. The complexity only appears when you start moving those answers somewhere else. Each tool on this page handles one step of that move.
- Get the responses out.Google Forms has no native “send to Slack” setting. You need an Apps Script bound to the form that fires on submission and POSTs the answer somewhere. Writing that script by hand is annoying; the generator emits a ready-to-paste version.
- Know what the response looks like.Once you've got submissions flowing, the next question is “what shape will my downstream code see?” The response formatter takes any pasted response and renders the Slack message and the Block Kit body so you can debug before going live.
- Get the field names right. The most common silent break: routing rules that reference a field name that no longer matches the form question title. The field extractor pulls the names verbatim from a real response so you can paste them into your rules without a typo.
- Test custom receivers. If your form posts to a custom server (not Slack directly), the webhook payload generator emits a sample body in the shape your endpoint will receive, plus a curl command to send it. Saves you 20 form submissions while you debug the receiver.
What we automate and what these tools cover
RouteForms is the managed version of this pipeline, install the Apps Script once, point it at us, and we handle the response parsing, routing rules, retry logic, and delivery log automatically. These free tools cover the same workflow at a lower level: they're what you reach for when you want to do part of it yourself, or debug what RouteForms is already doing.
The main guide at /google-forms-to-slack walks through the managed setup end-to-end. If you're weighing whether to use these tools alone or sign up, the roundup of real options is more useful than us pitching ourselves here.
Frequently asked questions
What are 'Google Forms tools' on this page?▾
Free, no-signup utilities for working with the Google Forms side of a forms-to-Slack pipeline. Each one solves one small piece of the data path: generating the Apps Script that posts submissions to a webhook, formatting raw response data into a Slack-ready message, pulling field names out of a response so you can paste them into routing rules, or generating a sample webhook payload for testing custom endpoints. Pick whichever matches the task in front of you.
Do I need a Google Forms account to use these?▾
Most of the tools are pure clients, paste data in, get output out. The Apps Script generator emits code you paste into a Google Form's Apps Script editor; that part needs a Google account with edit access to the form. The other three (response formatter, field extractor, webhook payload generator) work entirely on data you provide and don't touch Google at all.
Which tool should I use first?▾
If you're setting up a brand-new Google Form → Slack pipeline, the Apps Script generator is the starting point, it gives you the bridge between the form and a Slack channel. If you're stuck on routing because rule field names don't match the form questions, the field extractor is the fastest fix. If you've got raw response data from a log or a Sheet and want to see what the Slack message would look like, the response formatter is the path. If you're debugging a custom endpoint that's supposed to receive form submissions, the webhook payload generator emits the test bodies.
Are these tools alternatives or do they work together?▾
They compose. A typical setup: use the script generator to install the bridge, the field extractor to find the exact strings you need in your routing rules, the response formatter to verify the Slack message looks right, and the webhook payload generator only if you've got a custom server-side receiver in the mix. The Apps Script the generator emits also matches the payload shape the formatter handles, so you can debug both ends with the same shape in your head.
Why these specifically, and not other Google Forms add-ons?▾
Each one is a focused utility for one job, they're meant to be paste-and-go in under a minute. We don't try to do everything Google Workspace add-ons do (document generation, Calendar event creation, Sheets sync, email sending). For the broader 'do many things with a Google Forms submission' use case, Form Director or Zapier are better fits. RouteForms (the paid product behind these tools) is purpose-built for the Google-Forms-to-Slack hop with routing rules, retries, and a delivery log.
Do you store the data I paste in?▾
No. The Apps Script generator, response formatter, field extractor, and webhook payload generator all run entirely in your browser, what you paste never reaches our servers. The webhook checker (a related Slack-side tool) does make a request from our infrastructure on your behalf because it has to send the test to your webhook URL, but it doesn't retain the URL after the check.
Can these tools handle multi-select / checkbox answers?▾
Yes. Across all four, multi-select values are handled as comma-joined strings in the standard view (matching what the Apps Script generator emits to a webhook). The field extractor flags them as type 'multi' and suggests a 'contains' operator in the suggested routing rule. The payload generator's Apps Script event shape keeps them as arrays under namedValues to match the real Apps Script onFormSubmit shape.
Send Google Forms responses to Slack with routing
RouteForms is the managed version of the workflow these tools cover. Free for 30 responses a month.
Keep reading
The full index. Google Forms, Slack webhook, Apps Script, and lead routing categories.
The end-to-end overview: setup, routing, delivery monitoring, pricing.
The rule model, operators, ordering, the simulator, explained in detail.
All the real options for delivering Google Form responses to Slack, ranked by fit.