n8n Webhook Lead Scoring: Claude Haiku + HubSpot + Slack

Turn website form leads into scored, routed contacts—automatically

This n8n workflow receives website form submissions via webhook, uses Anthropic Claude Haiku to extract intent, then scores and tiers each lead (A/B/C). It upserts contacts into HubSpot, sends optional Slack alerts for Tier A, and logs every outcome to an n8n Data Table—including invalid leads and HubSpot sync errors.

What this workflow does

• Receives lead data via a webhook (or runs with sample payloads from a manual trigger).
• Normalizes and validates inputs: checks email format and detects common prompt-injection patterns.
• Handles invalid safely: invalid leads are kept with a reason instead of being dropped.
• Uses Claude Haiku for intent extraction: sends the free-text message to Claude Haiku to extract structured intent, timeframe, use case, and an injection flag.
• Scores and assigns tiers: computes a lead score, assigns Tier A/B/C with human-readable reasons, and zero-scores anything flagged as injection.
• Final consistency check before HubSpot sync.
• Upserts contacts in HubSpot with five custom properties, recording whether the HubSpot sync succeeded.
• Routes leads: Tier A can trigger a Slack alert (if enabled); Tier B/C enter HubSpot nurture lists. Work-email leads also trigger a HubSpot company lookup by domain and create the company if missing.
• Logs everything—including drops, injections, routing, and HubSpot errors—into an n8n Data Table and outputs a scorecard.

Use cases

• SaaS teams want instant lead scoring from website forms and automated CRM updates in HubSpot.
• Sales teams need Slack alerts for high-priority Tier A leads.
• Automation engineers want a robust webhook pipeline with prompt-injection detection and auditable logging.

Technical details

• Integrations/nodes: Anthropic Claude Haiku, HubSpot, Slack
• Workflow logic: if, code, merge, switch
• Output/record keeping: n8n Data Table log of processed leads and sync results