Contact-Form Lead Enricher: every form submission arrives pre-researched in Slack
An n8n workflow that catches your website's contact-form submissions via webhook, has Claude research the sender's company from their email domain and website, scores the lead, and posts a briefing card to Slack — so you walk into every reply already knowing who they are.
- 1
Catch the submission
A
Webhooknode receives the form POST (name, email, message). Add this URL in your form tool's integrations panel. Test with the form's own test-submit button and pin the sample data in n8n while you build the rest. - 2
Research the domain
A
Codenode extracts the domain from the email and short-circuits personal providers (gmail, outlook, yahoo → skip to step 4 flagged as 'personal'). For business domains, anHTTP Requestfetcheshttps://{domain}and anHTMLnode extracts the page text. - 3
Brief and score with Claude
An
HTTP Requestto Claude: the form message + homepage text in, JSON out — {company_summary, likely_role, size_hint, score, reasoning, suggested_first_line}. That last field drafts the opening line of your reply, referencing what they asked and who they are. - 4
Post the card and log it
A
Slacknode posts to #leads: name, email, score, summary, their message, and the suggested reply opener. AGoogle Sheetsnode appends the same for pipeline history. Median time-to-first-reply is the metric this whole recipe moves.
Frequently asked questions
How does it connect to my existing form?
Three common paths: point your form's webhook/integration setting (Typeform, Tally, Webflow forms all have one) at the n8n webhook URL; or add the URL as your form handler if it's custom-coded; or watch the notification email with a Gmail trigger as a fallback. The workflow starts at 'a submission arrived as JSON' — however it gets there.
What does the enrichment actually contain?
From the email domain, the workflow fetches the company homepage text and has Claude summarize: what the company does, rough size signals, the sender's likely role, and a lead score with reasoning — e.g. '7/10: agency owner, 10–20 staff, asking about exactly your mid-tier service'. Gmail/Hotmail senders skip enrichment and get flagged as personal.
Is researching a lead from their public website okay privacy-wise?
You're reading the public homepage of a company whose employee just contacted you — that's ordinary due diligence, the same thing you'd do manually. The workflow stores only the summary in your Slack/CRM. Don't bolt on scraping of personal social profiles; company-level context is all you need to reply well.