The form submits
Someone fills in your contact form. The lead's details exist — for about a minute.
WEBSITE ENQUIRY AUTOMATIONSee the build →
Website enquiries that never get missed.
Someone fills in your contact form. If nobody checks the inbox that day, the lead goes elsewhere by tomorrow. This workflow fires the submission straight to your team's Slack the moment it happens — name, message, details — and archives it in a sheet, so an enquiry never dies because the inbox wasn't watched.
01 / THE PROBLEM
The form isn't the problem. The gap after it is.
The enquiry arrives, sits in an inbox nobody checks, and the lead who needed an answer closes with whoever answered first.
The fix isn't a better form. It's an enquiry that can't be missed.
02 / WHAT IT ACTUALLY LOOKS LIKE
Slack fires instantly
A message lands in your team's channel the moment it happens: name, message, contact details. No checking, no delay.
It's archived
The submission is saved to a spreadsheet automatically, so nothing disappears when Slack scrolls past.
You answer while it's hot
The team sees it in minutes instead of days — and the lead is still yours when you reply.
03 / THE REAL COSTS & THE HONEST LIMITS
What it costs to run, and what it can't do.
- 01What you needn8n, a Slack workspace, and a website form that can send a webhook. Google Sheets and Gmail optional — they add the archive and the optional email response.
- 02How hard it isSimple — point your form at the webhook URL. One of the easiest setups on Botvent: two credentials and a channel name.
- 03What it can't doYour form must be able to send a webhook — if it can't, this won't work. It alerts, it doesn't reply or qualify. And it ships Slack-shaped: a team that lives in email can switch it, but expect a config change.
- 04What it isThe alarm for enquiries — not the follow-up. If leads arrive but never get chased, that's the next step, and it's a separate template.
04 / THE REAL WORK, VERIFIED
This is somebody's actual published work.
The workflow behind this page is real: a website lead capture system published in the n8n gallery by Marth, live and reachable at its source — Slack notifications on every submission, Gmail responses, and Sheets archiving. Botvent wrote it up as a listing — Marth has not claimed the page, so treat it as a pointer to their work, not an offer to be hired.
See the full listing, requirements & limits →- Live at its source — the original workflow is linked on the listing
- Every submission fires a Slack message instantly, with the lead's details
- Archived in a sheet — the record doesn't depend on a checked inbox
- Honest about the webhook requirement and the Slack-first shape
05 / QUESTIONS BUSINESSES ACTUALLY ASK
Before you decide, the honest answers.
How much does website enquiry automation cost to run?
The workflow itself is free. The running costs are: n8n (self-hosted free, cloud from ~$24/month), a Slack workspace (free tier is fine), and Google Sheets (free). The template has one of the smallest monthly bills on Botvent — mostly nothing.
Does my website form need to be special?
One hard requirement: the form must be able to send a webhook (POST the submission somewhere). Most builders — Typeform, Formspree, Gravity Forms, Webflow, Wix — can. If yours can't, that's the real blocker, and this page won't pretend otherwise.
We don't use Slack — will this still work?
It ships Slack-shaped: the template's channel is Slack. The guide describes switching the destination, so a team that lives in email can adapt it — but expect a small config change, and the published version is Slack-first.
Will it reply to the enquiry for us?
No — it alerts, it doesn't answer. That's the honest boundary. If the problem is follow-up after the enquiry — leads that arrive but never get chased — that's a different template: Botvent's lead-follow-up page handles the quiet chasing.
Won't enquiries just sit in spam anyway?
The point of the route is that it bypasses the inbox entirely: form → webhook → Slack means your email's spam filter never sees the message. If your form can't send a webhook, nothing on this page changes that.
How do I know it's actually working?
Send a test submission after setup — the Slack message lands within seconds. And the optional spreadsheet archive is the record that every enquiry arrived, so nothing depends on a checked inbox.