Pipedrive

The Pipedrive connection sends qualified, consented leads to the correct sales account and can connect explicitly linked deal outcomes to leadmaps analysis. Pipedrive remains the system of record for CRM-owned fields.

The existing Pipedrive connection completed its production authorization, delivery, duplicate-prevention, and disconnect canary on August 2, 2026. The customer-health extension has a separate release gate and remains a selected Business private beta. It is not generally available.

Pipedrive person sync is supported on Pro and Business. Business workspaces can also enable revenue outcome imports and an optional deal-writing recipe.

Choose the access you need

Pipedrive permissions are attached to the app shown during authorization. leadmaps uses a separate, fixed-permission connection flow for each access level so the approval screen stays truthful.

Access	Plan	What leadmaps can do
People	Pro and Business	Find or create a person for a qualified, consented lead and update only mapped leadmaps fields.
Revenue outcomes	Business	Read linked deal stage, status, value, currency, and close date for reporting.
Deal writing	Business	Create or update a linked deal only when you explicitly activate a deal recipe.
Customer health and lifecycle	Selected Business beta	Update only mapped organization health fields and reconcile explicitly mapped organization or deal statuses as trusted lifecycle changes.

People is the default. leadmaps does not create deals or activities unless an owner or admin selects and activates a recipe that requires deal access.

Connect Pipedrive

1. Open Settings, then Integrations.
2. Select Pipedrive and choose Connect.
3. Choose the access level for this connection.
4. Select the correct Pipedrive company and review the permissions.
5. Return to leadmaps and choose fields and deal stages by their Pipedrive names.
6. Preview the result with masked example data.
7. Activate the connection or rule when the preview is correct.

If an access level is temporarily unavailable, leadmaps will say so before opening Pipedrive. You can still choose another configured access level.

Only a workspace owner or admin can connect, reconnect, change mappings, or disconnect Pipedrive.

Choose fields and deal stages

The mapping editor loads the standard person fields and eligible custom fields from the connected Pipedrive company. Revenue and deal-writing connections also load active pipelines, stages, and eligible custom deal fields. You select the names shown in Pipedrive instead of finding or pasting field codes.

Deleted, unsupported, and read-only choices are not offered. If a saved field or stage is no longer available, leadmaps identifies it as unavailable, keeps the saved mapping unchanged, and requires a replacement before activation.

Use Reconnect if Pipedrive reports that the current authorization cannot load these choices. Reconnecting replaces the authorization for the same leadmaps connection and does not create a second connection.

Matching and duplicate protection

leadmaps first reuses a Pipedrive object it has already linked. If no link exists, it uses your configured external identifier or a consented email address. Ambiguous results stop safely for review. leadmaps does not choose an arbitrary person or merge Pipedrive records.

Retries and repeated callbacks reuse the same delivery identity. They do not create another person or deal for the same action.

Revenue outcomes

Business workspaces can import outcome fields from linked deals. These fields can appear in campaign, journey, and revenue analysis. leadmaps describes the relationship as an association and does not claim proven causation.

leadmaps ignores unrelated deals and does not overwrite CRM-owned fields. Changes with an older provider timestamp cannot replace a newer imported outcome.

Customer health and lifecycle

This access profile is available only to selected Business workspaces in the customer health private beta. It cannot be enabled by choosing a client-side option when the workspace is outside the beta.

An owner or admin configures:

1. A stable organization field containing the same explicit customer account identifier used by leadmaps.
2. Separate organization fields for the leadmaps health and lifecycle labels.
3. An optional Pipedrive organization or deal status field to import.
4. The exact provider status values that should become trusted lifecycle changes.

The mapping does not infer an organization from a person’s email domain. Missing, blank, or unmapped status values do not create a lifecycle event. Repeated provider results and retries reuse the same logical update, while older effective changes remain in history without replacing a newer account state.

Customer-health automations are configured separately in the Integration Hub. They remain opt-in and do not send session replay, page contents, or raw event properties to Pipedrive. Read Customer health and churn autopsies for the evidence and lifecycle boundary.

Reconnect or disconnect

Choose Reconnect when Pipedrive says Needs attention, when permissions change, or when you want another access level. A successful reconnect replaces the old authorization without creating a second connection. leadmaps removes the replaced authorization in the background using the same permission profile that created it.

Choose Disconnect to stop new deliveries, remove stored authorization, and release the connection slot. Existing Pipedrive records are not deleted.

Temporary provider failures and rate limits are retried. Delivery history shows whether an action is waiting, succeeded, needs attention, or stopped permanently.

Data and privacy

Only fields required by the active mapping are sent. Free-text page contents, session replay, visitor browsing history, payment fields, passwords, and provider secrets are never sent to Pipedrive through this connection.

When outcome matching is enabled, leadmaps uses only the identity fields that the owner or admin selected for the mapping. Other contact fields returned by the provider are ignored and are not stored in analytics events.

Before activating a mapping, confirm that you have a lawful basis for every contact field you send and that the destination’s access and retention settings match your privacy policy.