Qualify Contact Form 7 Leads with Gemini → HubSpot & Slack

Turn Contact Form 7 submissions into qualified leads—automatically

This n8n workflow uses Gemini to read every Contact Form 7 submission, classify it as lead, support, or spam, and route the results to HubSpot and Slack—so only high-quality prospects reach your CRM.

What this workflow does

• Receives form submissions securely: a New Lead Webhook receives Contact Form 7 fields as JSON from WordPress (after Contact Form 7’s own spam check). Header Auth keeps the endpoint private.
• Maps your form fields: a Lead Fields code step reads the configured email, name, and message fields, splits the name for HubSpot, and collects other fields (phone, subject, consent boxes) for Slack alerts.
• Gemini qualification: the workflow sends your business description plus the submission to the Gemini Chat Model. It returns:
  • a category: lead, support, or spam
  • a score from 1 to 5
  • a one-line summary
  The output is validated against a JSON schema.
• Prevents CRM pollution: spam never reaches your CRM. If Gemini fails or returns unexpected output, the lead is sent to sales without scoring—so outages don’t lose leads.
• Routes by verdict: lead submissions are saved to HubSpot with a note; support requests go to a dedicated Slack channel (Notify Support).

Use cases

• Qualify inbound traffic from Contact Form 7 and automatically enrich HubSpot with Gemini-scored lead notes.
• Send support requests to a separate Slack channel for faster triage, while filtering spam.
• Reduce manual lead review by distinguishing setup warnings (e.g., no email and no message) from real leads.

Technical details

• Integrations: WordPress → Webhook, Gemini Chat Model, HubSpot, Slack
• n8n nodes used: if, set, code, no op, slack, switch