Pharos Docs

Pipedrive

Functional guide for configuring the Pipedrive lead sync integration in Pharos.

This guide explains the Pipedrive integration in Pharos from a functional point of view.

What Is This Integration

The Pipedrive integration syncs Pharos leads into Pipedrive persons.

It is intended for teams that want lead capture and post-purchase contact enrichment in Pipedrive without manually recreating lead records.

When to Use It

Use Pipedrive when you want:

  • new or updated Pharos leads reflected in Pipedrive people records
  • lead records enriched again after a successful purchase
  • sales operations to manage follow-up in Pipedrive while leads originate in Pharos

Prerequisites

Before configuring Pipedrive, make sure:

  • you have a valid Pipedrive API token
  • you know your Pipedrive company domain or tenant subdomain
  • lead email addresses are captured reliably in Pharos

How to Configure It in Pharos

  1. Open the Pipedrive integration page in admin settings.
  2. Enable the integration.
  3. Enter the API token.
  4. Enter the company domain.
  5. Save the settings.

What Happens After It Is Enabled

After the integration is enabled:

  • Pharos syncs leads when they are created or updated
  • Pharos attempts to match Pipedrive persons by email first
  • once a person is found or created, Pharos stores the external person mapping for later updates
  • successful purchases trigger another sync for the linked lead when one exists

How to Verify It Is Working

You can verify the setup by:

  • creating or updating a lead in Pharos and confirming the person appears in Pipedrive
  • checking that later updates modify the same person instead of creating duplicates
  • confirming that a purchase tied to a linked lead triggers another person update

Limitations or Important Notes

  • v1 syncs persons only
  • v1 does not create deals, businesses, or manage stages
  • person matching depends primarily on email
  • if a purchase succeeds and no lead can be resolved, Pharos skips CRM sync for that purchase

Troubleshooting

If the setup does not behave as expected:

  • confirm the integration is enabled
  • confirm the API token and company domain are correct
  • confirm the lead has a usable email address
  • check the audit log for outbound integration requests

Functional Summary

The Pipedrive integration keeps Pipedrive people aligned with lead activity captured in Pharos, using email-first matching and follow-up sync after successful purchases.