Skip to content
Search prompts, tools, agents…

Form Submission to CRM Lead

Capture form submissions, create or update CRM contacts without duplicates, add an AI summary and alert your team, with a four-platform build guide and test plan.

Free 4 views 0 copies 0 downloads

This workflow captures website form submissions, creates or updates the contact in your CRM without duplicates, records where the lead came from, optionally adds an AI-written summary and priority, and alerts your team. It removes copy-and-paste work and speeds up the first response.

At a glance

Trigger A new form submission, received by a webhook or a form integration
Result A contact in the CRM, a note with the message, an alert in chat or email and a log entry
Platforms Make, Zapier, n8n, Power Automate
Difficulty Beginner to intermediate
Setup time 1 to 2 hours including testing
Human approval The team reviews each alert. The AI step only summarises.

What it does and does not do

It does It does not
Validate the email and avoid duplicate contacts Email the lead automatically
Save the message and source on the contact Decide whether a lead is good enough to contact
Summarise the message and suggest a priority Replace consent and privacy checks
Notify the right person Delete or merge existing records

Before you start

  • A form that can send data to a webhook or has a native integration with your automation platform.
  • A CRM account (for example HubSpot) and permission to create and update contacts. See the HubSpot MCP server page for related setup notes.
  • A chat or email destination for alerts.
  • A clear consent statement on your form and a privacy policy. Follow the data protection laws that apply to you.

Plan your fields

Form field CRM property (check your internal names) Notes
Email Email Required. Use it to find existing contacts.
First and last name First name, Last name Split a single name field if needed.
Company Company name Optional.
Message A note on the contact, or a custom “Latest enquiry” property Do not overwrite older messages.
Page or form name Lead source or a custom “Source page” property Helps later reporting.
Consent Marketing or communication consent property Only store true consent.

The AI instruction (optional step)

Read this enquiry and return ONLY valid JSON with these keys: {"summary": "", "topic": "", "priority": "", "reason": ""}.
- summary: one sentence.
- topic: one of sales, support, partnership, job, spam, other.
- priority: one of high, normal, low.
- reason: one short sentence explaining the priority.
Use only the text below. Do not guess details that are not present. If the message looks like spam, set topic to spam.
Enquiry: {{Message}}

Build steps

  1. Receive the submission through a webhook or form trigger.
  2. Validate. Check the email looks valid and not empty. Stop and log if it fails. Optionally filter obvious spam with a hidden “honeypot” field.
  3. Search the CRM for a contact with the same email.
  4. Create or update the contact. If none exists, create one. If it exists, update only fields that are empty or that you want to refresh.
  5. Add the message as a note or in a dedicated property, with the source and date.
  6. Optional AI step: summarise the message and set a priority. If it returns spam, skip the alert and tag the log.
  7. Alert the team in Slack, Teams or email with the summary, priority and a link to the CRM record.
  8. Log the run in a sheet: date, email, result and any error.

Platform guide

Step Make Zapier n8n Power Automate
Receive Webhooks: custom webhook, or your form app’s module Webhooks by Zapier: catch hook, or the form app trigger Webhook node “When an HTTP request is received” (premium) or a Microsoft Forms trigger
Validate Filter with a pattern or “exists” check Filter step IF node Condition action
Search and create or update CRM module: search contacts, then create or update CRM action: find contact, then create or update CRM node with a get or create-or-update operation HubSpot or Dynamics connector actions
AI summary An AI app module, then Parse JSON AI by Zapier or an AI app action AI node, then Code or Set node AI Builder action (if licensed) or an HTTP call, then Parse JSON
Alert Slack or Gmail module Slack or Gmail action Slack or Gmail node Teams or Outlook action
Errors Error handler on the CRM and AI modules Zap error notifications Error Trigger workflow Scope with “Configure run after”

Check the current names in your platform, and remember that some connectors and the HTTP action need paid licences on certain plans.

Test plan

Test Expected result
A new lead with all fields Contact created, note added, alert sent
The same email again Contact updated, no duplicate
An invalid email Stops and logs, no contact created
A spam-like message Tagged as spam and no alert to the team
CRM unavailable Error logged and an alert about the failure

Cost and limits

  • Each step or module counts toward your platform usage, and the optional AI step adds model cost.
  • High form volume or spam can use up your plan, so filter early.
  • CRM API limits can slow bursts. Retry with a delay.

Security and privacy

  • Only store personal data you need and have consent for.
  • Do not send sensitive personal data to an AI provider without checking your policy.
  • Restrict who can see the log sheet and alerts.
  • Use a dedicated integration user or app in your CRM with limited permissions.

Variations

  • Round-robin owner assignment: assign each new lead to the next salesperson in a list.
  • Business email check: route free-email addresses to a different queue.
  • Scoring: pass the lead to the Lead Qualification Agent for a fit and intent score.

Troubleshooting

Problem Fix
Duplicate contacts Search by email first and use create-or-update where available.
Missing fields Check the form’s field names match the webhook payload you mapped.
Too many spam alerts Add a honeypot field, a spam rule or a captcha.
Property not found Use the CRM’s internal property name, not the display label.

See the CRM Property Cleanup Planner, the CRM and Sales Prompt Pack and the New Lead Company Summary workflow.

Join the conversation

Your email address will not be published. Required fields are marked *