⭐ Available in the following bundle: Core Bundle (incl. in all plans)
⭐ Available on the following plans: Pro, Agency, Business
👀 Not sure which plan you're on? Check your subscription here.
Map Heyflow fields to HighLevel (GoHighLevel) fields to easily send information from your funnel to HighLevel and track incoming responses as contacts or companies. Follow up on new leads quickly and manage your sales pipeline more efficiently.
Important to note
❗ All data that you want to map needs to have a System Label set (alternatively, the field needs to be set as a variable)
❗ The information from your heyflow will overwrite existing High Level data (in case a contact already exists with the same email address or phone number).
Setup
Connecting your account
Within your funnel, go to “Connect” and then to the tab “Response Handlers”
Click on our HighLevel integration under CRM & Lead Management and “Add account”, a pop-up window will appear and ask you to provide your HighLevel credentials
After authenticating with HighLevel, click on “Select Account” and select the HighLevel account you would like to connect to Heyflow.
Choosing the entity
Select the HighLevel entity you want to create. You can choose between
Contacts and
Companies.
❗ It's only possible to send the data to one of these object types, not multiple.
Mapping data fields
Choose a Heyflow field and map it to the corresponding field in your integration. You can select from:
built-in fields like Heyflow ID, Response ID, Referrer, URL (with parameters), or A/B test ID and version;
a static text input to send fixed values (e.g. an identifier that will only be sent to the integration);
or any input field from your flow.
Repeat this process as needed. When the flow is ready, click on “Save changes”.
And that’s it, you will now receive your responses in HighLevel!
🔎 You can only forward individual file uploads, as each upload generates a single link. If you need to collect multiple files, you can add multiple Upload blocks to your flow. Learn more about Uploads here.
Tracking of URL parameters
If you want to pass URL/UTM parameters from your flow to HighLevel, you need to set up a hidden input field to capture the data. Once set up, you can map these input fields to corresponding fields in your response handler of choice.
The UTM parameters will then be automatically passed along with each response—without your visitors noticing. 🚀
Troubleshooting
If something goes wrong with your integration, an automatic email notification will be sent. The message includes the flow ID, response ID and a description of the error returned by your integration.
The entire response is omitted if a field is mapped incorrectly and HighLevel rejects the format. If responses are missing, and it’s not due to repeated contact details, check that each custom field is set up to receive the correct information.
🔎 For a list of common issues and general recommendations, check out the Troubleshooting Guide for Response Handlers.
I do not receive my test response
A common reason for missing test responses is that the same email address or phone number is used repeatedly for test submissions. In that case, HighLevel updates the existing contact instead of creating a new one, which makes it look like no response was received. Using a fresh email or phone number for each test avoids this issue.
I only see one upload link, but a user can upload multiple files
Currently, it's not possible to send multiple upload file URLs to HighLevel. Alternatively, when working with multiples files, please also use multiple blocks.
My date inputs are not correctly send to HighLevel
To ensure dates are formatted consistently between Heyflow and HighLevel, both systems must use the same date format. You can set the date format for Date Picker blocks in Heyflow. For instance, if HighLevel uses the American date format (MM/DD/YYYY), Heyflow Date Blocks should use the same format.
❗ Note: Date Picker masks can display dates differently from how they are stored.
How to Trigger a Workflow
To automatically trigger a HighLevel workflow based on Heyflow submissions, follow these steps:
Map the Heyflow ID to a HighLevel property
In your integration settings, make sure that the Heyflow ID is mapped to a contact property in HighLevel. For that, you may want to create a new one.
This allows you to identify which specific flow a contact submitted.
Create a new workflow in HighLevel
Go to Automation → Workflows → Create workflow.
Choose Start from Scratch.
Set up the enrollment trigger
Click Add New Trigger → Contact Created or Contact Updated
Add a filter for the specific Heyflow ID (the property you mapped earlier) to trigger the workflow only for a specific flow.
