The problem
Running several brands means several contact forms, each a potential leak. The default options all had a flaw: form plugins dumped submissions into an inbox where they got buried, hosted form services held our customer data on their servers and charged per submission as volume grew, and none of them told us instantly when a lead came in or where it came from. A lead that arrives Friday night and gets seen Monday is, for most intents, a lost lead.
The build
We built a single self-hosted n8n workflow that every brand's form posts to. The architecture is deliberately simple, which is why it's reliable:
Form submit → Webhook (capture + UTM) → Postgres (store) → branch:
├─ Mailgun (notify team + auto-reply to sender)
└─ Telegram (instant ping to phone)
Each stage earns its place:
- Webhook capture — the form posts JSON to a webhook endpoint. Crucially, the page captures UTM parameters into session storage on arrival and sends them with the submission, so every lead carries its source, medium, and campaign. We know which ad or channel produced it.
- Postgres storage — the lead is written as a structured row with the camelCase form fields mapped to snake_case columns. It's queryable, exportable, and ours — no third-party form service holding the data hostage.
- Mailgun notification — the team gets an email with reply-to set to the submitter, so a reply goes straight back to the lead. The sender simultaneously gets an automatic acknowledgement.
- Telegram alert — a formatted message hits our phones the instant the lead lands, so response time is measured in seconds, not hours.
- Conditional subscription — only when the consent box is ticked is the lead added to the mailing list, keeping the list clean and compliant.
The result
Zero leads lost to a buried inbox. Full source attribution on every submission, so marketing spend can be judged by leads produced rather than clicks bought. Customer data that lives in our own Postgres database on our own infrastructure, not a vendor's cloud. And a notification fast enough that we can reply while the prospect is still on the site. The whole pipeline runs at effectively no marginal cost per submission, because self-hosted n8n doesn't meter executions.
This is the workflow you can buy for $47 as a starting point — built to your form and handed to you as importable n8n JSON. It's not a template we dreamed up; it's the production pipeline running this site.
Why it matters for your build
The pattern generalizes. Swap Telegram for Slack, swap Postgres for your CRM, add an AI classification step that scores each lead before it routes, and you have a complete lead routing automation tuned to how your team sells. The point of starting with one workflow is exactly this: prove the pattern on something concrete, then extend it into the system. If you're currently paying per submission on a hosted form or automation tool, the same logic applies to a full Zapier to n8n migration.