How to Connect a GoHighLevel Form to an Automation Workflow

Connecting a form to an automation workflow is one of the most practical things you can do inside GoHighLevel. When set up correctly, every form submission automatically triggers a sequence of actions — sending a confirmation email, assigning the lead to a pipeline stage, notifying your team, and more. This guide walks you through the entire process step by step.

Understanding How Forms and Workflows Interact

In GoHighLevel, forms and workflows are separate tools that communicate through triggers. A form collects data from a contact; a workflow defines what happens after that data is received. The connection point is the Workflow Trigger, specifically the one called Form Submitted.

Before you start, make sure you have:

• A form already created under Sites → Forms → Builder (or at least a draft saved)
• A workflow created or started under Automation → Workflows
• A sub-account (location) where both the form and workflow live — they must be in the same location to communicate

If you are on a plan that does not include unlimited workflows or advanced automation features, some steps may look different or be unavailable. Check your plan details inside the platform.

Step 1 — Create or Open Your Workflow

1. Navigate to Automation in the left sidebar.
2. Click Workflows.
3. Click + New Workflow to start from scratch, or open an existing one you want to connect to your form.
4. If starting fresh, choose Start from Scratch or select a relevant template. Templates can save time but may include pre-built triggers you will need to adjust.
5. Give your workflow a clear name — something like Contact Form Lead Nurture helps avoid confusion when you have multiple workflows.

Step 2 — Add the "Form Submitted" Trigger

This is the step that creates the actual link between the form and the workflow.

1. Inside the workflow editor, click Add New Trigger (usually shown as a + Add Trigger button at the top of the canvas).
2. A panel will open on the right side. Search for or scroll to Form Submitted.
3. Select Form Submitted as your trigger type.
4. Under Filters, locate the Form dropdown and select the specific form you want to connect. If you leave this blank, the workflow will fire for every form submission in your location — which is rarely what you want.
5. Apply any additional filters if needed (for example, filtering by a specific tag or custom field value).
6. Click Save Trigger.

Tip: Using Multiple Triggers

A single workflow can have more than one trigger. If you want the same automation to fire when either a form is submitted or a survey is completed, you can add both triggers to the same workflow. Just be mindful of overlap — contacts could enter the workflow more than once if the re-entry settings allow it.

Step 3 — Build Your Automation Actions

With the trigger in place, you can now add the actions that will run after each form submission.

1. Click + Add Action below the trigger.
2. Common first actions include:

• Send Email — to confirm receipt to the contact
• Send Internal Notification — to alert your team via email or SMS
• Add to Pipeline — to move the contact into a CRM stage automatically
• Add Tag — to segment the contact for future automations
• Wait — to add a delay before the next action

1. Configure each action by filling in the required fields in the right panel. For Send Email, for example, you will need to select or build an email template.
2. Use Custom Values (the merge tag system) to pull data from the form — such as the contact's name or the specific option they selected — directly into your messages.
3. When your action sequence is complete, click Save at the top right.

Step 4 — Publish the Workflow and Test It

A workflow in Draft mode will not run, even if the trigger is configured correctly.

1. Toggle the workflow status from Draft to Published using the switch at the top of the editor.
2. Submit a test entry through your form using a real (or test) email address.
3. Go to Automation → Workflow Executions (or check the Contact record of your test submission) to verify that the workflow ran and each action executed as expected.
4. If the workflow did not fire, re-check that you selected the correct form in the trigger filter and that the form is published and accessible.

Common Errors and Troubleshooting

Even when the setup looks correct, a few issues come up repeatedly:

The workflow does not fire after form submission

• Confirm the workflow is Published, not in Draft.
• Confirm the Form Submitted trigger has the correct form selected in its filter.
• Check whether the contact already exists and whether Re-entry is disabled — returning contacts may be blocked from re-entering.

The contact is created but no actions execute

• Open the contact's activity timeline and look for workflow execution logs. An error message there usually points to a misconfigured action (e.g., a missing email template or an invalid pipeline stage).

Custom field data from the form is not populating in emails

• Make sure the form field is mapped to a Contact Field or Custom Field in the form builder (Field Settings → Map to). Unmapped fields do not get stored on the contact record and cannot be used as merge tags.

The workflow fires multiple times for the same submission

• Check whether re-entry is enabled and whether the form uses an embed code that could be submitting more than once due to a page reload or JavaScript conflict.

Form is embedded on an external site and data is not reaching GoHighLevel

• Verify the embed code is placed correctly before the closing </body> tag. If submissions still do not appear, check for Content Security Policy (CSP) restrictions on the external site.

---

Connecting forms to workflows is straightforward once you understand the trigger system, but it does require attention to the small configuration details covered above. If your automation needs are very simple — such as a single notification email — a third-party tool like Zapier or Make may actually be easier to manage. GoHighLevel's built-in workflow system becomes the clear choice when you need multi-step sequences, CRM pipeline integration, and tag-based segmentation all in one place.