Skip to content

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.)

  • Admin access to PartnerPortal
  • Access to the Pipedrive account you want to connect
  1. Open Integrations from the PartnerPortal sidebar.

  2. Click Enable Pipedrive.

  3. Sign in to Pipedrive or approve the connection if you are already signed in.

  4. After the connection succeeds, click Settings on the Pipedrive integration.

  5. Click Configure to open the mapping screen.

If Pipedrive asks you to reconnect, use the Reauthorize action from the integration settings instead of disconnecting and reconnecting from scratch.

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.

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.

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.

  1. In the mapping screen, find the Pipeline card under the Deal object.

  2. Open the card.

  3. Choose the Pipedrive pipeline you want PartnerPortal to sync.

The Pipedrive Pipeline card with a pipeline selected from the Value dropdown.

  1. Open the Stage card.

  2. Click Map Values.

  3. Map your PartnerPortal phases to the Pipedrive stages partners should see.

  4. 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
  5. Save the Stage card.

If you want to sync more than one Pipedrive pipeline, repeat the stage mapping for each extra pipeline.

  1. In the stage-mapping window, use the pipeline selector on the left to switch to the next pipeline.

  2. Map that pipeline’s Pipedrive stages to the PartnerPortal phases you want to expose.

  3. Repeat for any remaining pipelines.

The Pipedrive stage-mapping window with the pipeline selector on the left side.

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.

  1. In the object you want to map, choose the Pipedrive custom field from the dropdown.

  2. Click Add.

  3. Open the new field and set:

    • Type to Portal Object
    • Object to Lead
    • Field to the matching field from your lead form
  4. Save the mappings.

A Pipedrive text-field mapping with Type, Object, and Field set from a portal lead field.

  1. Confirm the dropdown field exists in both Pipedrive and the PartnerPortal lead form.

  2. Select that Pipedrive field in the appropriate object and click Add.

  3. Set:

    • Type to Portal Object
    • Object to Lead
    • Field to the matching PartnerPortal dropdown field
  4. Click Map Values and match each PartnerPortal option to the correct Pipedrive value.

  5. 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.

  1. In the Deal object, choose the Pipedrive destination field.

  2. Click Add.

  3. 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
  4. Save the mappings.

A Pipedrive Deal object field added for mapping partner data into a destination field.

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.

These settings live below the mapping interface on the Pipedrive configuration screen.

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.

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.

This setting controls what PartnerPortal should do if Pipedrive says the record already exists.

OptionWhat happens
ErrorPartnerPortal stops the create action and returns an error when Pipedrive detects a duplicate
AdoptPartnerPortal uses the existing Pipedrive record and continues tracking it

This setting controls what happens if one part of the multi-object create flow fails.

OptionWhat happens
Don’t CleanupObjects created earlier in the flow stay in Pipedrive even if a later object fails
CleanupPartnerPortal deletes the records it created in that flow if a later object fails to create