Automation and integrations decision

SlackNotify App

A small, single-developer replacement (Apps Script + webhook) is realistic and inexpensive to run; the vendor's value is convenience, billing, and marketplace integration rather than technical lock-in.

Visit website

Built by Sanskar Tiwari, who ships 8 products in this index

You pay

$3.25/mo

$39/yr

Read off the official pricing page.

You’d pay instead

$20one-off8 h to build

$0/mo2 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

  • Install a small Google Apps Script that listens for Google Form submissions, expands a message template using submission answers, and POSTs the result to a Slack incoming webhook.

What it still won’t have

  • Marketplace listing and discoverability (Google Workspace Marketplace)
  • Integrated paid licensing and billing/Stripe flow
  • Hosted account management UI and paid-support SLA
  • Multi-form dashboard and usage analytics across many forms
  • Brand, reviews, and one-click install experience

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 1 seat.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a Google Apps Script (Node-compatible Apps Script runtime) project that sends Slack notifications for Google Form submissions. Stack: Google Apps Script (server-side), PropertiesService or Google Sheet for config, simple HTMLService setup UI. In scope: (1) an installable trigger that runs on form submit, (2) a setup page where a user can save a Slack incoming webhook URL and a message template using {{question}} placeholders, (3) code to map FormResponse answers to template variables and produce a Slack payload (supporting plain text and basic markdown), (4) HTTP POST to the Slack webhook with retries and error logging, (5) unit tests or runnable test functions and basic runtime error handling and logging. Out of scope: marketplace publishing, paid subscription/billing flows, multi-account admin dashboard, analytics. Deliverables: deployable Apps Script project, README install steps, error handling for webhook failures (exponential backoff), and tests for template expansion and payload sending.
How we checked2 sources · 3/3 runs agreed · evidence score 86

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.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded