⭐ Available on the following plans: Pro, Agency, Business
👀 Not sure which plan you're on? Check your subscription here.
Map Heyflow fields to HighLevel fields to easily send information from your heyflow 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 HighLevel data (in case a contact already exists with the same email address or phone number).
Setup
Connecting your account
Within your heyflow, go to “Integrate” and then to the tab “Response Handlers”
Click on our HighLevel integration 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 object
Select the HighLevel object 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, 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
Form autofill issues or data not passing correctly
If your Heyflow forms are not autofilling correctly or failing to pass data to HighLevel, the issue may be with how variables are formatted in URL parameters. HighLevel requires variables in URLs to be denoted using an @ symbol rather than curly brackets.
Steps to Fix the Issue
Locate the redirect URL in your Heyflow setup where data is passed to HighLevel.
Replace any curly bracket {} notation in the URL with an @ symbol for the variables.
Save the updated URL and republish your Heyflow.
Example of Correctly Formatted URL
✅ Example of correctly formatted URL:
https://api.leadconnectorhq.com/widget/bookings?first_name=@name&last_name=@surname&phone=@phone&email=@email
Instead of:
https://api.leadconnectorhq.com/widget/bookings?first_name={name}&last_name={surname}&phone={phone}&email={email}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.