cdp menu

Customerlabs CDP Documentation

You are here:

(A ‘Source’ platform is one where data can be brought in from any platform into CustomerLabs CDP)  

Pipedrive is a sales management tool that helps visualize your sales pipeline and helps to make sure important activities and conversations won’t get dropped. Salespeople really like it because it’s easy to use and intuitive. And managers like it because they don’t need to nag their team to use their CRM. It also supports built-in forecasting, integrations with other software such as Google Apps, MailChimp and Zapier and a powerful API for those that like to “roll their own” software solutions. 

Marketing teams connect Pipedrive with CustomerLabs CDP to send their Organization, Users & Deals related information to create unified customer profiles in CustomerLabs CDP and sync the enriched customer data to all their favorite tools in their tech stack. 

Getting started

Here’s a step-by-step process that helps you connect Pipedrive with CustomerLabs CDP,

1. Login to CustomerLabs → Sources

CustomerLabs sources screen

2. Select Pipedrive from the list of Sources

Pipedrive integration as a source in the sources screen of CustomerLabs CDP

3. Click on Create source URL

Creating source URL for pulling data from Pipedrive into CustomerLabs CDP

4. Copy the Workflow URL provided 

Create a custom source using webhook URl in CustomerLabs CDP

5. Now log into your Pipedrive account and navigate to Tools & Integrations

Tools and integrations in Pipedrive

6. Under Tools & Integrations click on Webhooks.

7. Click on Create new webhook

Webhook creation in Pipedrive to send data to CustomerLabs CDP

8. Choose the desired Event action 

Creating a new webhook in Pipedrive

9. Then choose the desired Event object

Pipedrive event object selection for event creation

10. Then paste the copied Workflow URL from CustomerLabs CDP under Endpoint URL and click Save

Endpoint outside Pipedrive to send CustomerLabs webhook

11. Voila! Your Pipedrive account is now linked with CustomerLabs CDP 

Note: To bring multiple events objects, click on create new webhook & configure the objects using the same endpoint URL

Building Workflows in CustomerLabs CDP

Setting up a workflow in CustomerLabs CDP will allow you to receive notifications about changes that happen to your Pipedrive data in real-time. 

For example, you can set up a workflow that will trigger a notification to be pushed to the CustomerLabs CDP specified every time a person/organization/deal has been updated in your Pipedrive account.

Workflow #1 – How to send data to CustomerLabs CDP when a new user is created in Pipedrive

The below steps explain how you can filter and map incoming contact information from Pipedrive to Customerlabs CDP

1. Give a name to your workflow and before proceeding, create a test person in Pipedrive to get related data samples. Once a new user is created, click on Choose sample data.

Workflow setup screen of CustomerLabs CDP

2. Click on Fetch new data to see sample person data created in Pipedrive inside CustomerLabs CDP

Fetch new data in data selection inside CustomerLabs CDP

3. By clicking on View details you’ll be able to see a JSON format of the same

Data Selection to view the details of the data

4. Now Select this sample & move to the next step.

Raw data of a user data imported from Pipedrive

5. You can add your filter criteria to remove irrelevant information or simply skip this step.

Filter incoming data option showing create filter criteria in CustomerLabs CDP

6. Lastly, in the event configuration screen, you’ll be able to map the incoming data to their respective fields in CustomerLabs CDP

7. Give a name to your incoming event. You can select a predefined event name as shown below or give a custom name based on your requirements. (Note: Selecting dynamic will let you take the name of the incoming event directly)

Event configuration inside Customerlabs CDP to configure a new event for the data pushed from Pipedrive into CustomerLabs

8. User Identity mapping lets you combine all user-related events, since an incoming person has an email address & is assigned a Pipedrive Object ID we can select two identifiers (identify_by_email and user_id) from the drop-down and assign relevant values.

User identity mapping to map all the fields properly from Pipedrive to Customerlabs CDP

9. Repeat the same step as above to add Account level identifiers.

10. Once the user mapping is done, you can categorically map other incoming information into different buckets as shown below

Other attributes mapped screen in CustomerLabs CDP

Workflow #2 – How to send data to CustomerLabs CDP when a new Organization is created in Pipedrive

The below steps explain how you can filter and map incoming organization information from Pipedrive to Customerlabs CDP

1. Give a name to your workflow and before proceeding, create a test organization in Pipedrive to get related data samples. Once a new organization is created, click on Choose sample data.

Workflow setup inside CustomerLabs CDP.

2. Click on Fetch new data to see sample organization data created in Pipedrive inside CustomerLabs CDP.

3. By clicking on View details you’ll be able to see a JSON format of the same.

All details list of the data pulled from Pipedrive into CustomerLabs CDP

4. Now Select this sample & move to the next step.

Image showing the raw data of the user as a sample for the data pulled in from Pipedrive

5. You can add your filter criteria to remove irrelevant information or simply skip this step. The screenshot below shows the filter criteria created to send only two events into the workflow. 

Filter incoming data screen Customerlabs CDP

6. Lastly, in the event configuration screen, you’ll be able to map the incoming data to their respective fields in CustomerLabs CDP

7. Give a name to your incoming event. You can select a predefined event name as shown below or give a custom name based on your requirements. (Note: Selecting dynamic will let you take the name of the incoming event directly)

Event configuration in CustomerLabs CDP app

8. Account Identity mapping lets you combine all organization-related events, since an incoming organization has Pipedrive Object ID, you can use it to map them as shown below, 

Account identity mapping custom field object ID inside Customerlabs CDP App

9. Once the account mapping is done, you can categorically map other incoming information into different buckets as shown below,

Map all the other attributes for the data pulled in from Pipedrive into CustomerLabs CDP app

Workflow #3 – How to send data to CustomerLabs CDP when a new Deal is created in Pipedrive

The below steps explain how you can filter and map incoming deal information from Pipedrive to Customerlabs CDP

1. Give a name to your workflow and before proceeding, create a test deal in Pipedrive to get related data samples. Once a new deal is created, click on Choose sample data.

Workflow setup screen CustomerLabs CDP

2. Click on Fetch new data to see sample organization data created in Pipedrive inside CustomerLabs CDP. Click on View details you’ll be able to see a JSON format of the same.

Data selection screen customerlabs cdp

3. Now Select this sample & move to the next step

Raw user data for pipedrive data inside CustomerLabs CDP

4. You can add your filter criteria to remove irrelevant information or simply skip this step.

Filter incoming data in CustomerLabs CDP app

5. Lastly, in the event configuration screen, you’ll be able to map the incoming data to their respective fields in CustomerLabs CDP

6. Give a name to your incoming event. You can select a predefined event name as shown below or give a custom name based on your requirements. (Note: Selecting dynamic will let you take the name of the incoming event directly)

Event configuration inside CustomerLabs CDP app

7. User Identity mapping lets you combine all user-related events, since an incoming person has an email address & is assigned a Pipedrive Object ID we can select two identifiers (identify_by_email and user_id) from the drop down and assign relevant values.

User identity mapping inside CustomerLabs CDP

8. Account Identity mapping lets you combine all organization-related events, since an incoming organization has Pipedrive Object ID, you can use it to map them as shown below, 

Account identity mapping in CustomerLabs CDP

9. Once the user and account mappings are done, you can categorically map other incoming information into different buckets as shown below

Map other attributes in CustomerLabs CDP for all the data pushed from Pipedrive

Destination

Send incoming data to third-party apps to boost marketing effectiveness. Learn more about the destination tools that we support here

Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we improve this article?
How Can We Improve This Article?
Need help?
Table of Contents
CustomerLabs gives freedom, flexibility and wings to digital marketers.
Sign Up

Schedule a 1-1 Demo

Ecommerce

Unified data to boost ecommerce growth

B2B

Engage your customers across the funnel with a unified martech stack

SaaS
Saas

Increase product metrics with a unified martech stack

Agency
Agency

Scale your customers quickly with the right data