Free diagnostics tools
Diagnostic utilities for Google-Forms-to-Slack pipelines that aren't working as expected. Pre-flight checks before going live, error decoders that translate cryptic Slack and Apps Script responses into plain English, a guided troubleshooter for symptom-based diagnosis, and a printable checklist for the whole pipeline audit.
Setup Checker (pre-flight)
Pre-flight readiness dashboard, verifies the Slack webhook, Apps Script trigger, sample response, and routing rules in one screen with fixes per item.
Slack Webhook Tester
POST a test payload to your Slack webhook URL. Get HTTP status, latency, response body, and a plain-English diagnosis.
Apps Script Trigger Checker
Tell us your trigger's function, source, and event type. We tell you whether it'll actually fire on form submission.
Slack Webhook Error Decoder
Paste a Slack error (status code, response body, or error string like 'no_service'). Get plain-English explanation, common causes, and the exact fix.
Apps Script Error Decoder
Paste an Executions-log error or a daily-failure email row; get plain-English cause and fix. Authorization, quota, UrlFetchApp, runtime errors decoded.
Form-to-Slack Troubleshooter
A guided decision tree for diagnosing why your pipeline broke. Pick a symptom, answer one or two questions, get a concrete fix.
Diagnostic Checklist
Nine checks that catch most broken pipelines, ordered cheapest-first. Tick each off; the fix sits inline. Saves locally; printable.
Pre-flight vs post-mortem
Diagnostic tools split into two timelines. Pre-flight tools validate the pipeline before any real submission flows through; post-mortem tools help when something has already broken. Both belong in the same place because the underlying components, webhook, trigger, routing rule, message template, are the same; only the question changes.
- Pre-flight. Setup Checker is the all-in-one readiness dashboard. The single-component checks (Webhook Checker, Apps Script Trigger Checker) cover one layer at a time when you want to isolate a specific piece.
- Post-mortem. Slack Webhook Error Decoder and the Apps Script Error Decoder turn cryptic strings into plain English. The Form-to-Slack Troubleshooter walks a guided decision tree from a symptom to a failing layer. The Diagnostic Checklist is the printable audit version of the same questions.
A diagnostic decision flow
- Setting up a new form? Run the Setup Checker. Catches misconfiguration before the first real submission.
- Just changed a webhook URL? Webhook Checker. One layer, one question, ten seconds.
- Trigger not firing? Apps Script Trigger Checker. Validates the function / source / event-type wiring.
- Got a Slack error string in a delivery log row? Slack Webhook Error Decoder. Plain-English fix per error code.
- Apps Script Executions tab shows red rows? Apps Script Error Decoder. Authorisation / quota / runtime errors translated.
- Symptom is “something's wrong but I'm not sure what”? Form-to-Slack Troubleshooter. Pick the symptom; answer the next question; arrive at the failing layer.
- Doing a periodic audit? Diagnostic Checklist. Nine items, printable.
Diagnostics + the managed pipeline
RouteForms includes a per-form delivery log on every paid plan; rows surface the exact Slack response and let you click through to the relevant decoder. The standalone tools on this page are useful (1) before signing up, (2) when debugging a non-RouteForms pipeline, and (3) as a sanity check independent of the dashboard. They cost nothing to keep open in a tab.
The end-to-end pipeline guide lives at /google-forms-to-slack; the canonical setup walkthrough lives at /google-forms-to-slack-setup-guide; and /how-to-test-google-forms-slack-notification covers ongoing monitoring.
Frequently asked questions
What are 'diagnostics tools' on this page?▾
Utilities for figuring out why a Google-Forms-to-Slack pipeline isn't working as expected, or for verifying it before going live. Two shapes: pre-flight checks (the setup checker, webhook checker, trigger checker) run before the pipeline is live; post-mortem tools (the error decoders, troubleshooter, checklist) help diagnose when something's already broken. Each runs in your browser; nothing is stored.
Where should I start when a pipeline breaks?▾
Three lookups, in order. (1) Open the form's delivery log and find the failed row. The Slack response code or error string is the most important diagnostic signal. (2) Paste that string into the Slack webhook error decoder (or the Apps Script error decoder if the error came from the trigger side). (3) If the decoded explanation doesn't make the fix obvious, run the guided troubleshooter, it asks symptom-based questions and narrows to the layer that's failing. The setup checker is the right tool when you're not yet live and want to validate everything before submitting a real response.
How is the setup checker different from the troubleshooter?▾
The setup checker is proactive, verifies each piece of the pipeline (webhook URL valid, trigger registered, sample response handled, routing rules well-formed) in one pre-flight dashboard. Run it before going live, or after any config change. The troubleshooter is reactive, assumes something's already broken and walks a decision tree from a symptom (e.g. 'submissions reach Slack but go to the wrong channel') to the failing component. They cover different timelines of the same pipeline.
What if my error string isn't in the decoder?▾
The decoders cover the documented Slack and Apps Script error strings plus the common undocumented variants we've seen in real failures. If yours isn't recognised, that's a signal, either it's a new failure mode (let us know) or the string itself is wrong (Apps Script sometimes echoes upstream errors verbatim). The troubleshooter is the fallback path; it asks symptom questions rather than relying on the error string.
Can I use these tools without signing up for RouteForms?▾
Yes, every diagnostics tool is free, no-signup, runs in your browser. We built them because we needed them ourselves; sharing them is cheap. They work on any Google-Forms-to-Slack pipeline. RouteForms-managed, hand-rolled Apps Script, or third-party. The only RouteForms-specific value is the integration with the delivery log on paid plans, where rows link directly to the relevant decoder.
Is there a checklist I can run through manually?▾
Yes, the diagnostic checklist is exactly that. Nine checks ordered cheapest-first (each takes seconds), with the fix inline next to each item. It's the right surface when you want a printable audit rather than an interactive tool. The setup checker covers the same ground interactively; pick whichever shape fits how you work.
Skip the diagnostics, let RouteForms manage delivery
Delivery log, failure alerts, idempotent retries. Free for 30 responses a month.
Keep reading
The full index, every category and tool in one place.
Tools for the Slack side of the pipeline, preview, template, Block Kit builder.
Tools for the Apps Script layer. UrlFetchApp helper, routing-rules-to-script converter.
Pre-flight, live test, ongoing monitoring, the testing playbook these tools support.