CustomerLabs + Pipedrive Integration

Pipedrive is a sales management tool that provides visual pipeline management and forecasting capabilities. Integrating Pipedrive with CustomerLabs enables contact, organization, and deal event data to be ingested into CustomerLabs, where it is used to build unified customer profiles and enrich downstream marketing destinations.

The connection is established via Pipedrive’s native webhook mechanism using a CustomerLabs-generated endpoint URL.

Prerequisites

• An active CustomerLabs account
• An active Pipedrive account with access to Tools & Integrations

Part 1 — Connecting Pipedrive to CustomerLabs

Create the Pipedrive Source

1. In CustomerLabs, navigate to Sources and select Pipedrive from the list of available sources.

   
   

2. Enter a name for the source and click Create Source to generate the webhook endpoint URL.

   

Copy the Workflow URL

Once the source is created, copy the Workflow URL — this is the endpoint Pipedrive will use to send event data to CustomerLabs.

Configure Webhooks in Pipedrive

1. In your Pipedrive account, navigate to Tools & Integrations.

   

2. Select Webhooks from the integrations list.

   

3. Click Create new webhook.

   

Configure the Webhook

1. Select the Event action (e.g., added, updated, deleted).

   

2. Select the Event object (e.g., Person, Organization, Deal).

   

3. Paste the Workflow URL copied from CustomerLabs into the Endpoint URL field and save.

   

4. The webhook is now active. Pipedrive will begin forwarding events to CustomerLabs.

Note

To ingest multiple event objects (e.g., both Person and Deal events), create a separate webhook for each object using the same Endpoint URL.

---

Part 2 — Workflow Configuration

Each Pipedrive event object requires a separate workflow in CustomerLabs to define how incoming data is mapped to user identities and event properties.

Workflow 1 — New Person (Contact) Event

Fetch Sample Data

1. Trigger a test event in Pipedrive by creating a new Person record. Then, in the CustomerLabs workflow editor, click Fetch Sample Data to retrieve the incoming payload.

   
   

2. Select the sample data to use for configuration.

   

Apply Filters (Optional)

Configure filters to process only specific events or field values.

Configure the Event Name

In the Event Configuration section, enter a name for the incoming event (e.g., pipedrive_person_added).

Map User Identity

Map the fields that identify the user in CustomerLabs:

• Email — map to the Pipedrive person’s email field.

• User ID — map to the Pipedrive person’s unique identifier.

  

Map Account Identity

Map account-level identifiers to associate the contact with an organization in CustomerLabs.

Map Additional Properties

Map remaining Pipedrive fields to CustomerLabs event or user properties as required.

---

Workflow 2 — New Organization Event

Fetch Sample Data

Create a test Organization record in Pipedrive, then click Fetch Sample Data in the workflow editor to retrieve the payload.

Select the sample to use for configuration.

Apply Filters (Optional)

Configure filters to process only specific events or field values.

Configure the Event Name

Enter an event name for the incoming organization event (e.g., pipedrive_organization_added).

Map Account Identity

Map the account identity using the Pipedrive Object ID to associate the organization record with CustomerLabs account profiles.

Map Additional Properties

Map remaining organization fields to CustomerLabs properties as required.

---

Workflow 3 — New Deal Event

Fetch Sample Data

Create a test Deal in Pipedrive, then click Fetch Sample Data in the workflow editor to retrieve the payload.

Select the sample to use for configuration.

Apply Filters (Optional)

Configure filters to process only specific events or field values.

Configure the Event Name

Enter an event name for the incoming deal event (e.g., pipedrive_deal_added).

Map User Identity

Map the user identity fields — email and user ID — to associate the deal with a contact in CustomerLabs.

Map Account Identity

Map the account identity using the Pipedrive Object ID to associate the deal with an organization in CustomerLabs.

Map Additional Properties

Map remaining deal fields to CustomerLabs properties as required.

---

The Pipedrive source is now active. CustomerLabs will ingest Person, Organization, and Deal events from Pipedrive and use them to build unified customer profiles available for segmentation and forwarding to downstream destinations.

Quick Reference

Setting	Value
Connection Method	Pipedrive Webhook → CustomerLabs Endpoint URL
Webhook Location	Pipedrive → Tools & Integrations → Webhooks
Endpoint URL	CustomerLabs → Sources → Pipedrive → Workflow URL
Supported Objects	Person, Organization, Deal
Multiple Objects	Create one webhook per object using the same Endpoint URL