Integrate Pipedrive to easily send information from your heyflow to Pipedrive and track incoming responses as deals, contacts (people) or leads.
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 Pipedrive data (in case a lead or 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 “Connect to Pipedrive”, a pop-up window will appear and ask you to provide your Pipedrive credentials
After authenticating with Pipedrive, select the Pipedrive account you would like to connect to and click on “Choose Account”
Select the Pipedrive object you want to create, between Leads, Contacts (People) or Deals. It's only possible to send the data to one of these object types, not multiple.
Handle responses as Deals
In the Pipedrive integration tab, select “Deals”
Choose a Heyflow field and then select its corresponding Pipedrive counterpart
Repeat this process for all relevant fields and click on “Save changes” afterward
And that’s it, you will now receive your responses within Pipedrive as Deals!
Handle responses as Contacts (People)
In the Pipedrive integration tab, select “Contacts (People)”
Choose a Heyflow field and then select its corresponding Pipedrive counterpart
Repeat this process for all relevant fields and click on “Save changes” afterward
And that’s it, you will now receive your responses within Pipedrive as People Contacts!
Handle responses as Leads
In the Pipedrive integration tab, select “Leads”
Choose a Heyflow field and then select its corresponding Pipedrive counterpart
Repeat this process for all relevant fields and click on “Save changes” afterward
And that’s it, you will now receive your responses within Pipedrive as Leads!
URL Parameter Tracking
In order to map UTM parameters in Pipedrive, 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 Pipedrive, and you can easily pass on UTM parameters to your CRM tool, without your visitors noticing.