Free Google Apps Script tools

Free utilities for Google Apps Script, the JavaScript-like environment that runs bound to your Google Form and executes on form submission events. Two tools here: a trigger checker that verifies your trigger's function name, event source, and event type are the right combination for form-submit handling; and a translator that turns a set of IF-THEN routing rules into a runnable Apps Script that posts to different Slack webhooks based on the answer.

Google Forms has no native Slack integration. To get a submission into Slack, something has to listen for the form-submit event and POST a message to a Slack incoming webhook. Apps Script is the lightest-weight way to do that, a small script bound to the form, a single trigger, a UrlFetchApp.fetch call. Most tutorials end at 'paste this script'; these tools cover the parts that go wrong after the paste (trigger misconfig, missing dedupe, ad-hoc routing).

Function = onFormSubmit (a function you've written in the script that takes an event object and POSTs to Slack). Event source = 'From form' (because the script is bound to the form). Event type = 'On form submit' (because you want it to fire on submission, not on form open or edit). Anything else is wrong for this use case, the trigger checker walks you through verdicts on every combination.

People re-run their installer function, installFormBridge, setupTrigger, whatever it's called, without first deleting the old trigger. Apps Script doesn't warn you. The second trigger gets created and both fire on every submission, so Slack gets two messages per form response. The fix is mechanical: open Triggers (clock icon in the Apps Script left sidebar), delete the duplicate row. Our generated Apps Script wipes existing triggers before creating a new one to prevent this, but if you wrote your own installer, double-check.

The routing-rules-to-Apps-Script translator on this page is the answer when you want to keep everything in Apps Script, no external service, runs entirely on Google's infrastructure, deploy-and-forget. RouteForms is the right answer when you want operational visibility on top: a per-form delivery log, one-click retries on failed posts, idempotency so Apps Script retries can't double-post, and email alerts when delivery starts failing. The script gives you the routing; RouteForms adds the safety net.

No. Both tools emit ready-to-paste output, the translator gives you a complete Apps Script you paste into your form's script editor; the trigger checker gives you a configuration verdict in plain English. The Apps Script editor itself is where you'd need light JS familiarity if you wanted to modify the generated code, but the tools don't require it.

Both setups work but behave differently. Form-bound scripts get an event object with `e.namedValues` (a map of question to array-of-answers); Sheet-bound scripts get `e.values` (an array of cells in submission order). Most tutorials assume form binding, and so does our trigger checker. If you went the Sheet route, you'll need to read `e.values[1]` instead of `e.namedValues['Question']`. The routing-rules translator we ship outputs a form-bound script by default.