Skip to content

Template 01 · Free

Website lead form to CRM contact + Slack alert

What it automates

A website form submission becomes a HubSpot contact and a Slack alert. If HubSpot fails, the lead is emailed to you instead.

Last updated

Tested on: Not yet tested

The flow

STARTS WHENWebsite form posts to webhookCHECKClean and check email + spam trapSTEPCreate or update HubSpot contactRESULTSlack alert to your channelRESULTReply OK to the form

Who it is for

Service businesses whose website form currently lands in an inbox and gets copied into the CRM by hand.

Human approval

None needed: AI writes nothing a customer sees here. Customer emails are fixed text you edit in the workflow.

When something fails

HubSpot is retried 3 times; if it still fails, the full lead is emailed to you and the form still gets a success reply. Invalid emails and filled spam-trap fields get a 400 reply and create nothing.

Apps and accounts you need

  • HubSpotstores the contact (private app token) · official page
  • Slackposts the new-lead alert · official page
  • Gmailemails you the lead if HubSpot fails · official page
  • n8nruns the workflow (n8n Cloud or self-hosted)

Running cost estimate

At 100 form submissions a month: 100 executions a month fit n8n Cloud Starter (2,500 executions a month): €20/mo billed annually. Last verified on n8n's pricing page.

One run is one n8n execution, however many steps or waits it has. The cost of the apps themselves is separate. Make: no estimate until the Make version exists, because Make bills per module action.

Check n8n pricing on the official site

Plain link to n8n's pricing page. We have no affiliate relationship with n8n.

Setup overview

  1. In n8n, open Workflows, choose Import from File, and select n8n.json.
  2. Open the Configure me node and replace your email, Slack channel and lead-source label.
  3. Create credentials: a HubSpot private app token with contact write access, Slack, and Gmail.
  4. Copy the Lead form webhook's production URL and set it as your website form's POST target, with fields email, first_name, last_name, phone, message and an empty hidden field named website.
  5. Run one test with your own data, check every step's output, then switch the workflow to Active.

Known limits

  • No gap on n8n: every step uses a built-in node.

Platform status

n8n
Workflow file ready. n8n-mcp 2.94.0 validate_workflow (strict profile): 0 errors (Oct 17, 2026). Validation is not a live run.
Make
Make version in progress: blueprints are published only after they pass Make's own validator.