The integration can assign Owners, log messages as Notes or Activities, and write campaign information into Pipedrive fields. Each feature is configured in a different section.
User Mapping and Owners
Open Integrations, find Pipedrive and click Configure. In User Mapping you will find three sections.
Identities Mapping
An Identity is the Enginy profile that runs a campaign, such as a LinkedIn account or an email sender.
By associating an Identity with a Pipedrive user, Enginy can use that Owner when preparing a campaign's configuration. This association does not replace the Owner explicitly chosen on the campaign.
Users Mapping
Connects each user in the Enginy workspace with an active Pipedrive user. This relationship can be used as the default Owner when that user starts a manual export.
Enginy only shows Pipedrive users that are active and have not been deleted.
Default CRM owner
This is the workspace fallback Owner. It is used when an operation supports an Owner and none has been resolved through the operation itself or through User Mapping.
In a manual export, the usual precedence is:
The Owner chosen in the export window.
The Owner associated with the Enginy user.
Default CRM owner.
Important: The Owner does not change the account the integration uses. Every call to Pipedrive still uses the permissions and visibility of the user who authorized the OAuth connection.
Configuring Messages mapping
Messages mapping is in Sync Configuration.
Configuración de mensajes y creación opcional de Leads
You can choose separately how to log LinkedIn messages and emails. For each channel, select a Pipedrive Activity type or Note.
If you choose Note
Enginy creates a Note associated with the Person and, when available, with its Organization.
Note is the default value and is useful when you only want to keep the message content and context.
If you choose an Activity type
Enginy creates an Activity of the chosen type. The Activity is logged as completed and includes the subject, the content, the date and the available associations.
For the message to be logged, the contact must be related to a Pipedrive Person. If the contact's CRM identifier is missing, Enginy has nowhere to attach the Note or Activity.
Campaign Mapping
Campaign Mapping writes information from Enginy campaigns into Pipedrive Person fields. It does not create a Pipedrive campaign or filter.
You can map these groups of data:
Group | Information available |
Sequence | Sequence steps, engagement status, sequence status and reply analysis |
Opens, clicks, open analysis and click analysis | |
General | Campaigns, senders and activities |
Conversation Tags | Tags and tag categories |
For Campaigns and Senders, the configuration lets you keep the most recent value or add to the information already there. Review the behavior you choose so the field does not grow indefinitely.
The destination fields must be editable and compatible with the text or value Enginy sends. If you choose an options field, use only options Pipedrive allows.
Tasks
The Tasks panel only appears in workspaces that have the new Task Manager enabled.
When it is available, you can select which Pipedrive Activity types are treated as calls in Enginy. It is not a general mapping of every activity type.
Enginy can also create an Activity for a task associated with a Person or Organization, update it when the task changes, delete it when appropriate, and log a completed call as an Activity.
If the Tasks panel does not appear, there is nothing to configure. That feature is not enabled in your workspace yet.
Configuration recommendation
Map your regular users in
Users Mappingfirst.Set a
Default CRM ownerthat can receive records without a specific assignment.Review the Owner of each campaign.
Decide whether messages should be stored as a
Noteor as an Activity type.Map only the campaign data your team actually looks at.
Test an email, a LinkedIn message and a manual export.
Check the result on the Person and its Organization in Pipedrive.
If an activity does not appear
Check that:
The contact has an associated Person in Pipedrive.
Messages mappinghas a valid value.The selected Activity type is still active.
The OAuth user can create Notes or Activities.
The selected Owner is active and assignable.
The export or campaign finished without errors.
Check the Export Report and the Enginy activity history before repeating the operation.
When campaign fields reach Pipedrive
Two things changed here recently, and they are worth stating plainly because the old behaviour caught people out.
Campaign Mapping fields do not depend on message logging
Conversations CRM Export controls whether messages are logged as Activities or Notes. It does not control whether Campaign Mapping fields are written.
Important: The two used to be coupled. Turning conversation export off also stopped Sequence Status from updating, silently. They are now independent, and campaign fields mirror every send and reply whatever the message-logging setting says.
Sequence Status also syncs on enrollment, so it appears when the contact enters the campaign rather than only after the first message is logged.
Status also syncs on lifecycle changes
Status used to reach Pipedrive only on message events. It now also syncs when you:
Pause or resume a contact.
Block a lead.
Add contacts to a campaign, or remove them from one.
A blocked lead is reported with a blocked status rather than dropping out of the sync.
Good to know: These syncs never fail the action that triggered them. Pausing a contact still works if Pipedrive is unreachable, and the failure surfaces in the sync status instead.