How to Integrate Pipedrive with PartnerPortal
Use this guide to connect Pipedrive to PartnerPortal, understand how sync flows work, choose which pipeline should sync, and map the lead and partner data you want to send into Pipedrive. (Still comparing tools? See how PartnerPortal stacks up in our guide to the best PRM for Pipedrive.)
Connect Pipedrive
Section titled “Connect Pipedrive”Before you start
Section titled “Before you start”- Admin access to PartnerPortal
- Access to the Pipedrive account you want to connect
Connect your Pipedrive account
Section titled “Connect your Pipedrive account”Open Integrations from the PartnerPortal sidebar.
Click Enable Pipedrive.
Sign in to Pipedrive or approve the connection if you are already signed in.
After the connection succeeds, click Settings on the Pipedrive integration.
Click Configure to open the mapping screen.
Reauthorize Pipedrive
Section titled “Reauthorize Pipedrive”If Pipedrive asks you to reconnect, use the Reauthorize action from the integration settings instead of disconnecting and reconnecting from scratch.
Sync Direction
Section titled “Sync Direction”Portal to CRM
Section titled “Portal to CRM”When a lead is approved in PartnerPortal, the integration creates the mapped Pipedrive records and sends the portal data into those records based on your configuration.
CRM to Portal
Section titled “CRM to Portal”For each newly connected lead, PartnerPortal creates exactly three linked Pipedrive records: the Deal, the associated Person, and the associated Organization. After those records are linked, Pipedrive becomes the main source of truth for ongoing synced deal changes back into the portal.
If Sync Deal Details Back to PartnerPortal is enabled in CRM Settings below, changes to stage, close value, close date, and won/lost status in Pipedrive can flow back into the linked portal lead. Changes made in PartnerPortal do not sync back into Pipedrive. Pipedrive also does not support the separate Two-Way Sync setting that exists on the HubSpot integration.
Mapping
Section titled “Mapping”Every new synced Pipedrive lead creates those same three records: a Deal, its related Person, and its related Organization. The mapping screen controls how those records are populated and which pipeline and stages partners can see.
Map the Pipedrive pipeline
Section titled “Map the Pipedrive pipeline”In the mapping screen, find the Pipeline card under the Deal object.
Open the card.
Choose the Pipedrive pipeline you want PartnerPortal to sync.

Map deal stages
Section titled “Map deal stages”Open the Stage card.
Click Map Values.
Map your PartnerPortal phases to the Pipedrive stages partners should see.
In On Create, set Pipedrive CRM Stage to, choose how new portal deals should enter Pipedrive:
- Static stage: every new deal starts in the same Pipedrive stage
- Infer from mappings: PartnerPortal chooses the starting Pipedrive stage from your phase mappings
- Map manually: you choose an explicit starting stage for each portal phase
Save the Stage card.


Map additional pipelines
Section titled “Map additional pipelines”If you want to sync more than one Pipedrive pipeline, repeat the stage mapping for each extra pipeline.
In the stage-mapping window, use the pipeline selector on the left to switch to the next pipeline.
Map that pipeline’s Pipedrive stages to the PartnerPortal phases you want to expose.
Repeat for any remaining pipelines.

Map custom fields to Pipedrive
Section titled “Map custom fields to Pipedrive”Custom field mapping lets the values collected in PartnerPortal flow into the correct Pipedrive deal, person, or organization fields.
For the PartnerPortal side, most customer-facing lead fields come from your lead registration form. Connect the integration first, then come back here to map those fields.
Map single-line text fields
Section titled “Map single-line text fields”In the object you want to map, choose the Pipedrive custom field from the dropdown.
Click Add.
Open the new field and set:
- Type to Portal Object
- Object to Lead
- Field to the matching field from your lead form
Save the mappings.

Map picklist fields
Section titled “Map picklist fields”Confirm the dropdown field exists in both Pipedrive and the PartnerPortal lead form.
Select that Pipedrive field in the appropriate object and click Add.
Set:
- Type to Portal Object
- Object to Lead
- Field to the matching PartnerPortal dropdown field
Click Map Values and match each PartnerPortal option to the correct Pipedrive value.
Save the value mapping, then save the main mappings page.


Map partner data that is not on the lead form
Section titled “Map partner data that is not on the lead form”Some values belong to the partner rather than to the submitted lead form. In that case, you can map existing PartnerPortal partner data directly without adding another lead field.
In the Deal object, choose the Pipedrive destination field.
Click Add.
Open the field and set:
- Type to Portal Object
- Object to Partner Organization for company-level partner data, or Partner User for individual partner-user data
- Field to the exact partner value you want to send
Save the mappings.

Save mappings
Section titled “Save mappings”Click Save mappings at the bottom of the configuration page when you are done. The Pipedrive integration will begin syncing deals using the rules you just configured.
CRM Settings
Section titled “CRM Settings”These settings live below the mapping interface on the Pipedrive configuration screen.
Primary Object
Section titled “Primary Object”Pipedrive works best when Deal remains the primary object. That keeps the linked record in PartnerPortal centered on the deal while still creating the related person and organization alongside it.
Sync Deal Details Back to PartnerPortal
Section titled “Sync Deal Details Back to PartnerPortal”Turn this on when you want Pipedrive to update linked lead details in PartnerPortal after the records are created.
When enabled, Pipedrive can update:
- stage
- close value
- close date
- won/lost status
When disabled, PartnerPortal still creates and links Pipedrive records, but later changes in Pipedrive do not update the portal lead.
Duplicate Handling
Section titled “Duplicate Handling”This setting controls what PartnerPortal should do if Pipedrive says the record already exists.
| Option | What happens |
|---|---|
| Error | PartnerPortal stops the create action and returns an error when Pipedrive detects a duplicate |
| Adopt | PartnerPortal uses the existing Pipedrive record and continues tracking it |
Error Handling
Section titled “Error Handling”This setting controls what happens if one part of the multi-object create flow fails.
| Option | What happens |
|---|---|
| Don’t Cleanup | Objects created earlier in the flow stay in Pipedrive even if a later object fails |
| Cleanup | PartnerPortal deletes the records it created in that flow if a later object fails to create |