Google Forms to Slack troubleshooter
Pick a symptom. We narrow it down in a click or two and tell you the fix. Covers the failure modes we actually see, silent rule breaks from form renames, revoked webhooks, duplicate Slack posts from Apps Script retries, the lot.
What's the symptom?
The common failure modes
- Slack stopped getting messages. Was anything renamed, did the webhook rotate, did the trigger go missing? The tree narrows it down.
- Messages have the wrong content. Duplicates from Apps Script retries, missing fields from hidden questions, checkbox arrays rendered as raw JSON, two questions with the same title.
- Apps Script editor shows an error.First-time authorisation, wrong function selected in the dropdown, syntax error from a bad paste, UrlFetchApp can't reach the destination.
- Respondents see an error. The script threw, or the script is slow because the webhook receiver is slow.
- Routing went to the wrong channel. Rule ordering or a field-name mismatch.
- Setup help. Generator + install steps for a fresh form.
Every diagnosis names the exact log surface to confirm. Apps Script's Executions log, RouteForms's delivery log, Slack's incoming-webhook settings, so you can verify the fix worked.
Frequently asked questions
What does this tool do?▾
It's a small decision tree. Pick the symptom you're seeing. Slack stopped getting messages, messages have the wrong content, Apps Script editor shows an error, etc., and we walk you through two or three follow-up questions to a concrete diagnosis with steps to fix.
What kinds of failures does it cover?▾
The common ones: webhook revoked, form question renamed (silent rule break), Apps Script trigger missing, duplicate Slack posts from Apps Script retries, missing fields, checkbox arrays rendered as raw JSON, two questions with the same title, routing to the wrong channel, first-time authorisation, syntax errors from a bad paste, slow webhook receivers.
Does this tool need access to my form or Slack?▾
No. The troubleshooter is a guided checklist running entirely in your browser, no auth, no API calls, no data collection. It points you at the right place to look (the Apps Script Executions log, the RouteForms delivery log, etc.) but never reads or writes anything on your account.
What if my issue isn't in the tree?▾
Each diagnosis page ends with a 'still stuck, email support' link to /contact. We respond within one business day. Include the form name, what you were trying to do, and any error text from the Apps Script Executions log.
Where do most failures come from?▾
In our experience: form question renames silently breaking routing rules (the field name in the rule no longer matches), webhooks being revoked from Slack without RouteForms knowing, and Apps Script triggers getting deleted by an unrelated edit to the same form.
I'm setting up for the first time, should I use this tool?▾
There's a 'fresh setup' branch in the tree that points you at the right tools and guides, but if you're starting from scratch the /google-forms-to-slack guide and the Apps Script generator are more direct.
Want operational visibility before things break?
RouteForms's per-form delivery log records every Slack delivery with status code + retry button. Most of the failure modes above are visible in the log before you notice them in Slack.
Keep reading
POST a test payload to your Slack webhook URL and see the response decoded into plain English.
If routing went to the wrong channel, paste the submission and the rules here and see which one fires.
Re-generate the script if the current one was corrupted by a bad paste.
The end-to-end setup walkthrough if you're starting from scratch.
All the real options for this hop. RouteForms, SlackQ, Form Director, Zapier, Make, Apps Script, raw webhooks, ranked by fit.