Integrations
Pipedrive
Sync deals from Pipedrive as customers in LealUp — automatic mapping of name, value, status, and health.
The Pipedrive integration pulls deals from your Pipedrive account and turns them into customers inside LealUp. Ideal if you already use Pipedrive as a CRM and want LealUp to work on top of the same reality without re-entering data.
What it does
- Deals → customers. Each deal in Pipedrive is mirrored as a customer in LealUp.
- Automatic mapping. Name, value (MRR), status, and initial health score are calculated from the deal fields.
- Contact. The Person linked to the deal (name, email, phone) lands on the customer as the primary contact.
- Continuous sync. When something changes in Pipedrive — stage, value, close date — LealUp refreshes the customer.
What it does NOT do (v1)
- No manual mapping UI. Mapping is predefined (see the table below). Custom fields are not supported yet.
- Not bidirectional. Changes you make in LealUp (notes, tasks, health score) do not reflect in Pipedrive.
- Doesn't create deals. LealUp reads existing deals; it doesn't write back to Pipedrive.
- Doesn't sync activities. Calls and meetings from Pipedrive are not imported to the timeline (on the roadmap).
How to connect
- Settings → Integrations → Pipedrive → Connect.
- OAuth flow with Pipedrive — you authorize LealUp to read deals and persons.
- LealUp runs an initial backfill of active deals.
- From there on, sync runs automatically in the background.
The connection is per workspace (all users in your LealUp see the same synced customers).
Field mapping
This is how Pipedrive fields become LealUp customer fields:
| LealUp field | Pipedrive source | Notes |
|---|---|---|
name | deal.org_name (fallback: deal.title) | If the deal has no organization, the title is used |
contact_name | deal.person_name | Linked Person on the deal |
contact_email | deal.person_email | Primary email of the Person |
contact_phone | deal.person_phone | Primary phone of the Person |
mrr | deal.value | Deal value is assumed monthly |
subscription_status | deal status → status | See "Status mapping" below |
health_score | deal status → heuristic | See "Initial health score" below |
renewal_date | deal.expected_close_date (only if deal is won) | Null while the deal is open |
Status mapping
| Pipedrive deal status | LealUp subscription_status |
|---|---|
won | paid |
open | trial |
lost | churned |
Initial health score
A simple heuristic based on the deal status — meant as a starting point, not the final score:
| Pipedrive deal status | Initial health_score |
|---|---|
won | 80 |
open | 50 |
lost | 10 |
Once the customer is synced, LealUp's own health model (Engagement + Sentiment + Support + Product usage) takes over and the score evolves based on real signals. The imported score is only the initial state.
Assumptions that might not fit your case
- Deal value = monthly recurring revenue (MRR). If in your Pipedrive
valuerepresents annual contract value (ACV) or one-time revenue, themrron the customer will be off. Workaround: adjust manually on the customer record after the sync, or wait for custom field mapping (roadmap). - One deal = one customer. If you have multiple deals for the same company in Pipedrive (e.g., one per product line), each creates a separate customer in LealUp. Use Customers → Merge to consolidate if needed.
- Lost deals = churned. A lost deal in Pipedrive marks the customer as
churnedin LealUp. If you use "lost" for other reasons (disqualified lead, not a real customer yet), reconsider whether this integration fits.
Security
- OAuth with minimum scopes needed to read deals and persons.
- We store an encrypted OAuth token; nothing else.
- Revoke anytime from Pipedrive (Settings → Apps) or from LealUp (Settings → Integrations → Pipedrive → Disconnect).
Common issues
"I don't see my deals as customers"
- Check that the sync completed — the integrations page shows the last sync timestamp.
- If you have a lot of deals (thousands), the initial backfill can take a while.
- Confirm the integration status is Connected (not "Error" or "Expired token").
"The mrr is wrong"
- Pipedrive's
deal.valueis treated as monthly. If your values are annual or one-time, they'll import incorrectly. - Workaround: edit the customer manually, or request the custom field mapping feature at [email protected].
"The contact is missing"
- Only deals with a linked Person in Pipedrive bring contact data.
- If the Person has no email or phone in Pipedrive, those fields come in empty.
"The status doesn't match what I see in Pipedrive"
- LealUp reads the deal status (
won/open/lost). If you use custom stages that don't map cleanly to those, the status might not reflect your pipeline semantics. - Roadmap: custom stage mapping.
Disconnect
Settings → Integrations → Pipedrive → Disconnect
- Revokes the OAuth token against Pipedrive.
- Synced customers stay in LealUp (history is preserved).
- Future changes in Pipedrive no longer sync — customers stop updating.
- If you want to delete the imported customers too, go to Customers → filter by origin: Pipedrive → bulk delete (double confirmation required).
Roadmap
- Custom field mapping (map Pipedrive custom fields → LealUp custom fields).
- Activities sync (calls, meetings) to the customer timeline.
- Bidirectional: LealUp notes and tasks reflecting in Pipedrive.
- Custom stage → status mapping.
If any of these is blocking for you, let us know at [email protected] to help us prioritize.