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).
Initial Setup
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.
Select the HighLevel object you want to create, between contacts and companies. It's only possible to send the data to one of these object types, not multiple.
Handle responses as contacts
In the HighLevel integration tab, select “Contacts”
Choose a Heyflow field and then select its corresponding HighLevel counterpart
Repeat this process as needed. When the flow is ready, click on “Save changes”.
And that’s it, you will now receive your responses within HighLevel as Contacts!
Handle responses as companies
In the HighLevel integration tab, select “Companies”
Choose a Heyflow field and then select its corresponding HighLevel counterpart
Repeat this process as needed. When the flow is ready, click on “Save changes”.
And that’s it, you will now receive your responses within HighLevel as companies!
Tracking of URL parameters
In order to map UTM or URL parameters in HighLevel, via Heyflow, it is not enough to simply have them in your responses. You require something more “tangible”, something like… a block!
In this case, we’ll have to use input fields. You’ll simply define the variable as the name of the respective UTM parameter (i.e. “utm_source”, “utm_medium”, etc.) and, preferably, hide the block, since you don’t want the visitors of your flow to see these fields:
This allows you to map these input fields, and link them to fields in HighLevel, and you can easily pass on UTM parameters to your CRM tool, without your visitors noticing.
Troubleshooting
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.
I can't map my Heyflow signature to the HighLevel signature field
Currently, it's not possible to send multiple upload file URLs to HighLevel. To allow multiple file uploads, please create a Heyflow Upload block and HighLevel Upload custom field for each file.
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.