Pipedrive is a sales-focused CRM built around pipeline management. Follow the steps below to connect Pipedrive to Enginy and configure the integration.
To set up your Pipedrive integration:
Go to Integrations and open the All tab (or the Disabled tab).
Locate the Pipedrive card and enable it using the toggle switch.
Click the Configure button on the Pipedrive card.
A floating setup window opens with four sequential steps.
Important: You can only have one CRM integration active at a time. If another CRM is already active, disable it first.
Step 1: Sync Configuration
This step defines how Enginy matches contacts and companies with your Pipedrive records to prevent duplicates and ensure data integrity. A sync means Enginy compares its records against Pipedrive records using the identifiers you configure here.
Integration User
It shows whose email address is the API integration user.
Contact Identifier
Choose how Enginy determines whether a contact already exists in your Pipedrive.
Option | Matching Logic |
First name + Last name + Company name | A contact matches when all three fields are the same in both Enginy and Pipedrive. |
LinkedIn profile URL OR First name + Last name + Company name | A contact matches if the LinkedIn profile URL is the same or all three name/company fields match. |
Custom Mapping | Map an Enginy column to a Pipedrive field. This will be used for matching contacts or companies in Pipedrive. |
Note: Only one Custom mapping can be configured.
Company Identifier
Choose how Enginy determines whether a company already exists in your Pipedrive.
Option | Matching Logic |
Domain | Matches on the company domain (e.g., |
Domain or Company Name | Matches if either the domain or the company name is the same. |
Website | Matches on the company website URL (e.g., |
Website or company name | Matches if either the company website URL or the company name is the same. |
Custom Mapping | Map an Enginy column to a Pipedrive field. This will be used for matching contacts or companies in Pipedrive. |
Note: Only one Custom mapping can be configured.
General
Under General, you'll find two toggles that control how associations are handled during export:
When exporting contacts, associate them with companies in Pipedrive: If enabled, Enginy will automatically link exported contacts to their corresponding companies in Pipedrive.
When exporting companies, associate them with contacts in Pipedrive: If enabled, Enginy will automatically link exported companies to their related contacts in Pipedrive.
Pipedrive specific configuration
The Pipedrive integration includes additional settings that are not available in other CRM integrations.
Messages mapping allows you to configure how Enginy maps outreach activity types to Pipedrive activity types.
Create Leads from Contacts and Create Leads from Companies are two independent toggles. When enabled, Enginy automatically creates a Lead in Pipedrive linked to the exported contact or company.
Step 2: Field Mapping
This step configures which Enginy fields map to which Pipedrive fields when exporting data. The setup is split into two tabs — Contacts and Companies — and the mapping configuration works the same way in both.
Pipedrive-specific feature: In Step 2, you can also configure field mapping for Leads — this additional tab is only available for Pipedrive and is not present in other CRM integrations.
Field Types
Field Type | Description |
Enginy Fields | Standard fields from your contact or company lists (e.g., Phone Number, Job Title). Click Add field to add a new mapping: select the Enginy field first, then the corresponding Pipedrive field. |
Fixed Value Fields | Fields that always export with the same static value. For example, create a field called "Source" with fixed value "Enginy" so every exported record is tagged with its origin. |
Manual Export Fields | Fields whose value you define at the time of export. Click Add field, select the Pipedrive field to be set when exporting. As many as you want. |
Engagement Fields | Fields populated when an Activity is created in Pipedrive (e.g., an email sent, a LinkedIn message, or a Task log). Select the Pipedrive field and set the Value to export. Only one can be set. |
Warning: Don't map a Company field in the Contacts tab (or a Contact field in the Companies tab). This can cause export errors. If you must map the same field in both tabs, make sure it's mapped the same in both places.
In each Pipedrive field mapping dropdown, you'll see small status icons indicating whether the mapping is supported, not supported, or supported with limitations / a workaround.
Icon | Meaning |
Blue check | The mapping is okay, has no potential problems. |
Yellow exclamation | The field types in Enginy and Pipedrive may be incompatible (e.g., an Enginy Text field mapped to a Pipedrive Enumeration field). |
Red X | The mapping can't be applied because the types don't match — or because the Pipedrive field is read-only and can't be updated. |
Note: Some yellow warning icons appear when the selected Pipedrive field is an enumeration (dropdown) field. Your Enginy text field can still export successfully as long as the value matches one of the allowed dropdown options (using internal names, not label names).
Workaround: Create an AI Variable with output type = One off and define output tag options to exactly match the Pipedrive dropdown values — using internal option names (not labels).
Mapping Options
Option | Behaviour |
Enginy overwrites Pipedrive | Changes in Enginy automatically overwrite the corresponding fields in Pipedrive. |
Sync with Pipedrive | Data only syncs automatically when the destination field is empty, preventing overwriting existing values. |
Export Options
To export contacts or companies to Pipedrive, select the records you want to export from your list, click Export, and choose Export to CRM.
The export modal allows you to configure the following options before exporting:
Owner — Select a Pipedrive user as the owner of the exported records. You can also check Overwrite existing value to replace the current owner in Pipedrive.
Export associated company — When enabled, Enginy exports the contact's associated company alongside the contact.
Overwrite existing values — Expand this section to see each mapped field (split into Contacts and Companies tabs). Check Overwrite existing value next to any field to replace its current value in Pipedrive during export. When unchecked, the existing Pipedrive value is preserved and only empty fields are populated.
Once ready, click Export to send the records to Pipedrive. You can also click Review Mapping to verify your field mapping before exporting.
Step 3: Campaign Mapping (Optional)
This step lets you sync campaign-specific properties to Pipedrive. These are not standard list fields; they are properties tied to campaign activity.
Sequence
Property | What It Contains | Example Value |
Campaign Sequence Details | The steps included in the campaign. |
|
Campaign Engagement Status | The current status of each lead in the campaign. |
|
Sequence Status | The overall status of the campaign sequence for the lead. |
|
Campaign Reply Analysis | Indicates per-message whether the lead replied to each automated message. |
|
Email
Property | What it Contains | Example Value |
Campaign Opens | Total number of times a lead has opened one or more emails in the campaign. |
|
Campaign Clicks | Total number of times a lead has clicked a link in campaign emails. |
|
Campaign Open Analysis | Indicates per-message whether the contact opened that specific email. |
|
Campaign Click Analysis | Indicates per-message whether the contact clicked a link in that specific email. |
|
General
Property | What it Contains | Example Value |
Campaign | All Campaign names the contact has been added to. |
|
Senders | All sender names that have contacted the contact. |
|
Activities | All activities that have occurred with the contact. |
|
Conversation Tags
Property | What it Contains | Example Value |
Conversation Tags | All conversation tags applied to the contact (comma-separated). |
|
Conversation Tags Categories | Categories of conversation tags: POSITIVE, NEUTRAL, NEGATIVE (comma-separated). |
|
Step 4: User Mapping
This final step defines the associations between Enginy users/identities and Pipedrive users so that exports and activity logs are attributed to the correct people.
Identities Mapping
An Identity in Enginy is the profile that runs a campaign (for example, a LinkedIn profile or an email sender). Identities Mapping links each Enginy identity to a Pipedrive user.
When a campaign performs a sync or export, the Pipedrive activity log shows the associated Pipedrive user as the one who executed the action.
Users Mapping
Users Mapping links an Enginy user account to a Pipedrive user. This sets the default owner for any record exported by that user — even for automatic exports via field mappings, not just manual exports.
If Pipedrive users have different permission levels, this association respects those limits. A record exported by an Enginy user is owned by the mapped Pipedrive user and governed by that user's permissions.
Default CRM owner
This mapping sets a default Pipedrive owner (contact or company owner) for exports performed by an Enginy user who isn't mapped in User Mapping.
Save Your Configuration
After completing all four steps, click Update to save your Pipedrive configuration.