Forms Builder in HighLevel

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers how the HighLevel Forms Builder works, the available field types, how submissions map to the CRM, conditional logic, form completion actions, and how to connect forms to automated follow-up.

Reading time: about 8 minutes.

What Is the Forms Builder in HighLevel?

The Forms Builder is HighLevel’s drag-and-drop tool for creating forms – lead capture forms, contact forms, intake forms, booking request forms, and any other form where a contact submits information online.

Every form submission in HighLevel is a CRM event. The data submitted creates or updates a contact record automatically.

No spreadsheet export, no Zapier connection, no manual data entry. The contact lands in the CRM the moment the form is submitted.

That native CRM connection is what makes HighLevel forms significantly more useful than a standard embedded form that emails submissions to an inbox. Every submitter becomes a trackable contact with a full interaction history.

Find the form builder at Sites, then Forms in any sub-account.

Field Types

The form builder supports a comprehensive range of field types covering the full spectrum of data collection needs.

Standard contact fields – first name, last name, email, phone, address – are pre-mapped to the corresponding CRM contact fields. Adding these to a form ensures submitted contact information lands in the right place without any additional configuration.

Text fields handle short single-line inputs and long multi-line text inputs for questions that require an open-ended answer.

Choice fields – dropdown select, radio buttons, and checkboxes – present the respondent with a list of options. Dropdown and radio allow one selection.

Checkboxes allow multiple selections.

Specialty fields include date picker, file upload, signature, rating scale, and hidden fields. Hidden fields pass values into the contact record without displaying them to the submitter – useful for tracking source parameters or pre-populating fields from URL parameters.

Custom HTML can be added anywhere in the form for custom formatting, text blocks, images, or embedded content that does not fit standard field types.

CRM Field Mapping

CRM field mapping is what makes HighLevel forms more than just a data collection widget.

When a contact submits a form, every field value is mapped to a corresponding field in the contact’s CRM record. Standard fields are mapped automatically – email goes to the Email field, phone goes to the Phone field.

Custom fields require a matching custom contact field to be created in the sub-account settings first, then selected in the form builder as the destination for that form field’s submissions.

If the email address submitted already exists in the CRM, the submission updates the existing contact rather than creating a duplicate. If it is a new email, a new contact is created with the submitted data.

This deduplication behavior and automatic field mapping mean every form submission results in a clean, structured contact record – ready for segmentation, automation, and follow-up without any manual cleanup.

Conditional Logic

Conditional logic makes a form smarter by showing or hiding fields based on what a respondent has already entered.

A field can be configured to appear only when a specific answer is given to a previous field. A text field asking “Please specify your other goal” only appears when the respondent selects “Other” from a dropdown.

A field asking “How long have you been a customer?” only appears when the respondent indicates they are an existing customer rather than a new inquiry.

This keeps forms focused – respondents only see questions that are relevant to their situation. A form with conditional logic can handle multiple scenarios without presenting every possible question to every respondent.

For more complex branching across many steps, the Survey builder handles the experience better. But for forms with 1 to 3 conditional fields, the form builder’s conditional logic covers the need without switching tools.

Form Completion Actions

After a contact submits a form, the experience resolves to a completion action – a thank-you message, a redirect URL, or both.

A thank-you message on the same page confirms the submission. This is the minimum completion experience – at least confirm that the form went through rather than leaving the user staring at a submitted form with no feedback.

A redirect URL sends the submitter to a specific page after completion. A lead capture form can redirect to a booking calendar – the lead completes the form and is immediately invited to schedule a call.

An inquiry form can redirect to a resource or confirmation page that continues the funnel.

The redirect approach converts the form submission from a terminal action into a funnel step – the submitter moves forward rather than stopping at “thank you.”

Embedding on Websites

Every HighLevel form has a standalone hosted page URL and a website embed code.

The standalone URL is a HighLevel-hosted page containing only the form. Useful for sharing in emails or SMS messages when the recipient should complete the form without navigating to a specific website page.

The embed code is a JavaScript snippet that places the form inline on any website page – WordPress, Squarespace, Wix, Webflow, or a custom HTML site. The embedded form looks and behaves like a native element of the page while submitting data directly to HighLevel.

Submissions from embedded forms behave identically to submissions from standalone pages – the same CRM contact creation, the same workflow triggers, the same data mapping.

Submission Workflows

Form submission workflow integration is where HighLevel forms become significantly more powerful than generic form tools.

The Form Submitted trigger in Workflow Builder fires when any submission is made to a specific form. A workflow on this trigger can send a lead confirmation email, apply a tag based on submitted values, add the contact to a pipeline stage, notify the relevant team member, start a nurture sequence, or trigger any other automated action.

Multiple workflows can be triggered by the same form submission event. A lead capture form can simultaneously: send the contact a confirmation email, notify the sales team, add the contact to a pipeline, apply a source tag, and enroll the contact in a nurture sequence – all from a single form submission.

This automation chain is what closes the gap between “someone filled out the form” and “the right follow-up happened within minutes.”

Forms vs. Surveys – When to Use Each

Both collect data and store it in the CRM. The decision comes down to question count and the experience that produces the best completion rate for the use case.

Use a form when the data collection is short – 3 to 7 fields – and a single-page layout is appropriate. Lead capture forms, contact forms, quick inquiry forms, and booking request forms all fit this pattern.

The familiar single-page form layout is fast and expected for brief submissions.

Use a survey when data collection is longer – 8 or more questions – and the step-by-step experience of seeing one question at a time will produce better completion rates. Client onboarding questionnaires, qualification surveys, feedback surveys, and research questionnaires fit this pattern.

For most lead capture scenarios, a form is the right tool. For most client intake or qualification scenarios, a survey is better.

When in doubt on a medium-length questionnaire – 5 to 10 fields – test both formats and see which produces a higher completion rate for the specific audience.

What Can You Do With It?

• Capture leads from your website directly into the CRM: Every website form submission creates a contact – no import, no spreadsheet, no third-party integration required. The lead is in HighLevel the moment the form is submitted.
• Replace third-party form tools like Typeform or Gravity Forms: For most use cases, the HighLevel form builder handles what those tools do – with the added benefit that submissions go directly into the native CRM rather than requiring a Zapier connection.
• Fire automated follow-up within seconds of form submission: A workflow triggered by Form Submitted sends the lead a confirmation, notifies the sales team, and starts a nurture sequence before the submitter has closed the browser tab.
• Collect structured data with fields that map to CRM records: Custom fields in the form map to custom contact fields in the CRM – collecting specific qualification data like service interest, budget range, or timeline in a structured way that can be used for segmentation and targeting.
• Redirect submitters to the next step in the funnel: A form completion redirect to a booking calendar, a resource download, or a sales page keeps the funnel moving rather than ending at a static thank-you message.
• Use conditional logic to reduce form length for each respondent: Show only the fields relevant to each respondent’s situation – a shorter, more relevant form produces higher completion rates than a longer form where many questions do not apply.

Key Definitions

Use Cases by Industry

Marketing Agencies – Lead Capture

An agency builds a lead capture form for a local home services client’s website. The form collects name, email, phone, service type (dropdown), and a brief description of the project.

Conditional logic shows an “Urgent?” radio field only when the service type selected is a repair rather than an installation.

On submission, a workflow sends the lead a confirmation, notifies the business owner via SMS, and adds the contact to the Hot Lead pipeline stage. Urgent submissions get a separate notification tagged as priority follow-up.

Result: Every website lead becomes a structured CRM contact with source data, service interest, and urgency level – ready for immediate follow-up without any manual data entry.

Real Estate

A real estate agent embeds a property inquiry form on each listing page. The form collects name, email, phone, and a hidden field that pre-populates the property address from the page URL parameter.

When the form is submitted, the hidden field value tags the contact with the specific property they inquired about.

The workflow on submission notifies the agent, applies a “buyer inquiry” tag, and starts a property follow-up sequence with property-specific content.

Result: The agent knows exactly which property each lead inquired about from the moment the form is submitted – without relying on the submitter to specify it manually.

Medical Practices

A dental practice’s website contact form collects name, email, phone, and the type of appointment needed (dropdown: new patient, cleaning, emergency). The form redirects to the booking calendar after submission – the patient goes straight from inquiry to scheduling without an intermediate follow-up call.

The Form Submitted workflow applies a tag based on the appointment type selection and notifies the relevant staff member for each type.

Result: The form + booking calendar redirect eliminates the phone call step for many new patient inquiries. The patient books themselves. Staff is notified. The appointment is on the calendar before anyone makes a call.

Fitness and Personal Training

A personal trainer’s website has a “Start Your Free Consultation” form with name, email, phone, and three questions: primary goal (dropdown), current activity level (radio buttons), and availability (checkbox – morning, afternoon, evening). The form submission triggers a workflow that sends a welcome email with a booking link for the free consultation call.

The trainer sees the contact’s goal and availability in the CRM before the call. The first conversation starts with context rather than intake questions.

Result: The trainer starts every discovery call knowing the prospect’s goal and when they are available. The consultation is more focused and more likely to convert.

E-commerce and Online Brands

An e-commerce brand uses a HighLevel form for a “VIP Waitlist” for a product launch. The form collects email, first name, and how they heard about the brand (dropdown).

Submissions trigger a workflow that tags contacts as waitlist members and enrolls them in a pre-launch nurture sequence.

The source dropdown data lets the brand see which acquisition channels are driving the most waitlist sign-ups without any additional analytics setup.

Result: The waitlist generates structured CRM contacts with source attribution built in – ready for a segmented launch day campaign without any data cleanup.

Who Is This For?

How to Build a Form in HighLevel

Step 1: Open the Forms Builder

Go to Sites, then Forms in the sub-account navigation.

Click Create Form. Give the form a descriptive internal name – Lead Inquiry Form, Contact Us, New Patient Request.

Step 2: Add fields to the form

From the field type list, drag fields onto the canvas or click to add them. Start with the standard contact fields – first name, last name, email, phone – which are pre-mapped to CRM fields.

Add additional fields for any other data the form should collect.

Step 3: Configure each field

Click any field to open its settings. Set the label, placeholder text, required status, and any answer options for choice fields.

Use specific, clear labels that tell the submitter exactly what to enter – “Business Phone Number” rather than “Phone.”

Step 4: Map custom fields

For custom fields not in the standard contact field set, confirm they are mapped to the correct CRM custom contact field in the field settings.

If the required custom contact field does not exist yet, create it in Settings, then Custom Fields first, then return to the form builder.

Step 5: Configure conditional logic if needed

For any field that should only appear based on a previous answer, set up the conditional display rule in that field’s settings.

Test the logic mentally – trace each answer path to confirm the right fields appear for each scenario.

Step 6: Set the completion action

In the form settings, configure the completion: thank-you message, redirect URL, or both.

If redirecting to a booking calendar or next funnel step, confirm the destination URL is correct before publishing.

Step 7: Style the form

Customize button color, form background, and field styling to match the website’s design.

An embedded form that does not match the website’s visual style draws attention to itself as a third-party widget. Match the colors and make it feel native to the page.

Step 8: Build the submission workflow

In Workflow Builder, create a workflow triggered by Form Submitted for this specific form.

Add lead confirmation email, team notification, tag application, pipeline assignment, and any other automation that should fire immediately on submission.

Step 9: Embed and test

Copy the embed code from the form settings and paste it into the website page. Submit a test entry using a personal email.

Confirm the contact appears in the CRM with all fields correctly mapped. Confirm the workflow fires.

Fix any issues before the form goes live with real traffic.

How Does It Connect to HighLevel?

• Workflow Builder: The Form Submitted trigger in Workflow Builder connects every form submission to the full automation system. Lead follow-up, tag application, pipeline assignment, and team notifications all fire automatically on submission.
• Surveys: The Survey builder is the parallel tool for longer questionnaires. Forms and surveys share the same field types and CRM storage behavior but serve different use cases – forms for short data collection, surveys for multi-step questionnaires.
• File Upload Fields: File Upload Fields are available in forms – collected files are stored in the contact’s CRM record alongside the other submitted data.
• Funnel Builder: Forms can be added to any step in a HighLevel funnel – placing the lead capture form directly within the funnel page flow rather than on a separate standalone page.
• Tag-Based Automation: Form submission workflows apply tags from submitted values. Tag-Based Automation uses those tags to route contacts into appropriate nurture sequences based on what they selected in the form.

Common Questions

What is the Forms Builder in HighLevel?

A drag-and-drop tool for creating forms at Sites, then Forms. Every submission creates or updates a CRM contact automatically.

The Form Submitted workflow trigger enables automated follow-up on every submission.

Where do I find the Forms Builder in HighLevel?

Go to Sites, then Forms in the sub-account navigation. Click Create Form to open the builder.

What field types are available in the HighLevel Forms Builder?

Text (short and long), email, phone, dropdown, radio buttons, checkboxes, date picker, file upload, signature, address, hidden fields, rating scale, and custom HTML. Standard contact fields are pre-mapped to CRM fields.

Does HighLevel Forms Builder support conditional logic?

Yes. Configure conditional display rules to show or hide fields based on previous answers. A field can be set to appear only when a specific value is selected in another field.

Where are form submissions stored in HighLevel?

In the CRM contact record – creating a new contact or updating an existing one based on email address match. Also viewable in the form’s Submissions tab at Sites, then Forms.

Can a form submission trigger a workflow in HighLevel?

Yes. Use the Form Submitted trigger in Workflow Builder, select the specific form, and add any automated actions – lead email, team notification, tag application, pipeline assignment, nurture sequence enrollment.

Can I embed a HighLevel form on my website?

Yes. Every form has an embed code for placement on any external website.

Submissions from embedded forms behave identically to standalone form page submissions – same CRM storage, same workflow triggers.

What happens when someone submits a form in HighLevel?

The submitted data maps to CRM contact fields – creating a new contact or updating an existing one. Form Submitted workflow triggers fire.

The completion action (thank-you message or redirect URL) is presented to the submitter.

Can I create custom fields in HighLevel forms?

Yes. Create custom contact fields in Settings, then Custom Fields.

Once created, they are available in the form builder and can be added to forms. Submitted values store in the contact record under the custom field.

Can I use HighLevel forms for intake and onboarding?

Yes, for short-to-medium intake – up to about 10 fields. For longer intake questionnaires (10 to 20+ questions), the Survey builder typically produces better completion rates with its one-question-per-screen format.

To Wrap It Up

The forms builder is one of the most fundamental features in HighLevel because it is how most new contacts enter the CRM. Every lead capture form, contact form, and inquiry form on a client’s website is an entry point into the contact database.

The difference between a HighLevel form and a standard third-party form is what happens to the submitted data. A standard form emails it to an inbox or writes it to a spreadsheet.

A HighLevel form creates a CRM contact, maps the data to structured fields, fires a workflow, and triggers follow-up – all within seconds of submission.

That automation chain is what makes forms genuinely valuable rather than just convenient. The form does not just collect a name and email.

It starts the relationship – confirmation email, pipeline assignment, nurture sequence – before any human is involved in the process.

Here is how to get started:

1. Go to Sites, then Forms and click Create Form
2. Add the standard contact fields – name, email, phone – as the foundation
3. Add any additional fields for data relevant to the specific form’s purpose
4. Map custom fields to the correct CRM contact fields
5. Add conditional logic for any fields that should only appear based on previous answers
6. Configure the completion action – at minimum a thank-you message, ideally a redirect to the next funnel step
7. Style the form to match the website’s visual design
8. Build a Form Submitted workflow with lead confirmation, team notification, and pipeline assignment
9. Copy the embed code and place it on the website
10. Submit a test entry and verify the contact, workflow, and confirmation all fire correctly

Build the workflow before the form goes live – not after. Contacts who submit the form before the workflow is active miss the automated follow-up.

A lead who submits at 11pm and receives nothing until a team member manually follows up the next morning is a different experience than one who gets a confirmation email within 60 seconds. The workflow is what makes the form worth having.