Automation and integrations decision
Slacknotify
A single developer can build and maintain a Google-Apps-Script-based notifier covering the paid product's core features in a weekend; the vendor's hosted conveniences and marketplace listing are the main things you'd give up.
Visit website↗$3.25/mo
$39/yr
Read off the official pricing page.
$20one-off16 h to build
$0/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 1 seat.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- On Google Form submit, read responses, render a user-defined template, and POST a Slack webhook payload.
What it still won’t have
- Hosted billing, subscription management, and marketplace listing
- Support and fast bug-fix turnaround from the vendor
- Polished UX and pre-built templates
- Google Workspace Marketplace reviews/installs trust signal
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a Google Forms → Slack notifier as a Google Apps Script project: stack = Google Apps Script (server-side JS) + Apps Script HTML Service for settings UI. In scope: (1) an installable onSubmit trigger that reads form responses, (2) a settings page where a signed-in Google account can enter and save a Slack webhook URL and a message template with {{question}} placeholders (save per Google account via PropertiesService), (3) template rendering that replaces placeholders with submitted answers, (4) POST to Slack webhook with optional markdown payload, (5) error handling, logging to Stackdriver/Logs, and automated tests where possible (unit tests for template renderer). Out of scope: paid billing/subscription handling, Marketplace publishing, multi-user team billing. Include input validation, retries for transient HTTP failures, and at least 5 unit tests covering template rendering and webhook payload formation.How we checked
How the score was reached
- Build verdict base78
- 2 cited sources+1
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score86
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 2
Every page the run actually retrieved.
- official productSlackNotify App — home
- official pricingSlackNotify.app Pricing
Integrity checks
What held up, and what did not.
