Short answer
Build the form in GoHighLevel, map every answer to a contact field, then create a workflow with the Form Submitted trigger and the Form Is filter. Add Assign To User, then the internal notification. The trigger fires on every submission, so plan for repeats and check Contact Duplication Preferences.
In this post
What should a lead capture form collect?
The minimum needed to follow up: a name, an email or phone number, and one structured question that drives routing, such as the service wanted. Every extra field costs completions. Ask only what the team will use.
Use a drop-down or radio select for anything the workflow will branch on. Free text creates three spellings of the same answer. And decide what the visitor sees afterwards, because the confirmation is part of the form.
How do answers reach the CRM?
Forms write to contact fields. HighLevel documents that only contact custom fields appear in forms and contact workflows, so a deal-level value cannot be collected directly. See contact vs opportunity custom fields.
Before you publish, make a field map: question, destination field, required or not, format, and the workflow or report that reads it. A question can look right on the form and still write to the wrong field. Check the saved contact, not the preview.
How do you trigger a workflow from the form?
Create a workflow and choose the Form Submitted trigger. Its filter is Form Is, where you select the specific form. One workflow can respond to several forms if you add more filters.
Two limits matter:
- The trigger works with forms built in the CRM. For an external tool, you need an integration or a webhook to capture submissions.
- It fires on every submission, so the same person can start it repeatedly. HighLevel suggests conditions or cooldown periods to manage that. There is no built-in re-entry setting described for this trigger.
In email steps you can merge contact and custom-field values, such as the service the person picked. Add conditions to catch missing required answers.
What happens when the same person submits twice?
That depends on Contact Duplication Preferences, under Settings, Business Profile Settings. With Allow Duplicate Contact turned off, a form submission updates the existing contact, matched by email or phone, instead of creating another. Turned on, a new contact can be created. See how to find and merge duplicate contacts.
Decide the rule for returning customers too. A second inquiry might update the contact, open a new opportunity, or go to a person.
How should the submission be routed?
Keep routing simple and write it down first.
| Case | Route | Fallback |
|---|---|---|
| Service A requested | Assign to the Service A owner | General intake owner |
| Service B requested | Assign to the Service B owner | General intake owner |
| Service blank | Send to manual review | Never guess |
| Existing owner | Keep owner and notify them | Team lead |
Use Assign To User for the contact, with Only Apply to Unassigned Contacts on if returning contacts may re-enter. Put the internal notification after the assignment, so it reaches the new owner. Full detail is in how to assign new leads to the right team member.
Keep the notification short and include a link to the record. Send only the personal data the recipient needs.
How do you build it step by step?
- Create the form and add the minimum fields.
- Map each field to a contact field.
- Write the confirmation message.
- Create the workflow with Form Submitted and Form Is.
- Add conditions for each route and for missing values.
- Add Assign To User, then the notification.
- Create or update the opportunity if your process calls for one.
- Publish only after testing.
How do you test the whole journey?
Use test contacts with your own details. Submit the form six ways: all fields filled, a missing field, an existing contact submitting again, each service route, a blank optional field, and the same test contact twice. After each, check the confirmation, the contact fields, the owner, tags, the opportunity, the notification and the execution log. Confirm nothing reached a real prospect. The method is in how to test a workflow before it goes live.
Frequently asked questions
Should every submission create an opportunity?
No. Follow your sales process. A returning customer may need an update or a person, not a new deal.
Can an outside form trigger the workflow?
Not with the Form Submitted trigger alone. Use an integration or a webhook to bring the submission in.
What if a visitor leaves an optional field blank?
Give the workflow a fallback branch, and test it so the lead is not lost or assigned by guesswork.
If you want the form, routing and notifications built and tested, see the services page or book a free 30-minute call.
Sources: HighLevel Help: Form Submitted workflow trigger; HighLevel Help: Contact deduplication preferences; HighLevel Help: Assign To User action. Checked against the Help Center on 29 October 2026.
Want this set up for you?
30 minutes, a clear next step.
Anis Mahmud Anik
HighLevel Certified Admin. I set up and automate GoHighLevel for founders and owners.



