Library

Templates

Enrich new Pipedrive contacts with FullEnrich

Enrich new Pipedrive contacts with FullEnrich

Clay

Automatically enrich every new Pipedrive contact with verified emails, phone numbers, and LinkedIn profiles using FullEnrich, then update the contact with the enriched data.

Automatically enrich every new Pipedrive contact with verified emails, phone numbers, and LinkedIn profiles using FullEnrich, then update the contact with the enriched data.

Zapier

What this Zap does: When a new person is created in Pipedrive, FullEnrich finds the contact's verified email and phone number, then updates the same Pipedrive person with the enriched data. The Zap uses 3 steps: Pipedrive New Person → FullEnrich Enrich Contact → Pipedrive Update Person.

Use this Zap

1. Prepare your Pipedrive setup

Make sure your Pipedrive person records include the following fields:

  • First Name

  • Last Name

  • Organization (company name)

  • Email (will be filled by FullEnrich)

  • Phone (will be filled by FullEnrich)

2. Open the Zap template

Click the Use this Zap button above to open the template in Zapier. The Zap contains 3 pre-configured steps:

  • Trigger: Pipedrive - New Person (instant)

  • Action 1: FullEnrich - Enrich Contact

  • Action 2: Pipedrive - Update Person

3. Configure the Pipedrive trigger

Click on the first step (New Person). Connect your Pipedrive account. This is an instant trigger — the Zap fires immediately when a new person is created in Pipedrive, with no polling delay.

4. Connect your FullEnrich account

Click on the second step (Enrich Contact). Connect your FullEnrich account using your API key. Map the following fields from the Pipedrive trigger:

  • Name of Your Enrichment → e.g. Pipedrive

  • First Name → First Name from Pipedrive

  • Last Name → Last Name from Pipedrive

  • Company Name → Organization Name from Pipedrive

  • Domain of the company → Organization Domain from Pipedrive (if available)

  • Enrich with → Emails + Phones

5. Configure the Update Person step

Click on the third step (Update Person). Connect the same Pipedrive account. Map the following fields:

  • Person → ID from the Pipedrive trigger step

  • Email → Most Probable Email from FullEnrich

  • Phone → Most Probable Phone from FullEnrich

6. Test and turn on

Click Test step on each step to verify everything works — create a test person in Pipedrive first. Check that the Email and Phone fields get updated correctly. Once confirmed, click Publish to turn the Zap on. Every new person will now be automatically enriched.

Note: This trigger is instant — the Zap fires immediately when a new person is created in Pipedrive. No polling delay.

Problem

Solution

FullEnrich returns no email

Make sure First Name, Last Name, and Company Name are mapped correctly. Adding the Organization Domain improves match rates.

Pipedrive update fails

Check that the Person ID is mapped from the trigger step, and that your Pipedrive account has write permissions.

Zap doesn't fire

Make sure the Zap is published. Create a new person in Pipedrive (not edit an existing one) to trigger it.

Company name missing

Make sure the person is linked to an Organization in Pipedrive before creation, so the company name is available for enrichment.

Make

What this scenario does: When a new person is created in Pipedrive, FullEnrich finds the contact's verified email and phone number, then updates the same Pipedrive person with the enriched data. If no result is found, the field is set to "N/A".

3 modules: Watch Persons (polling) → FullEnrich Enrich → Update a Person

Get template

1. Watch Persons (trigger)

Go to make.com and click Create a new scenario. Add the first module: search for Pipedrive and select Watch Persons. Connect your Pipedrive account. Set Trigger when to add_time (triggers on newly created persons) and the Limit to 2.

2. FullEnrich - Enrich

Add a second module: FullEnrich → Enrich. Connect your FullEnrich API key. Map the fields from the Watch Persons module:

  • First Name → {{1.first_name}}

  • Last Name → {{1.last_name}}

  • Domain → the company domain (from the person's organization)

Under Enrich with, select Emails and Phones.

3. Update a Person

Add a third module: Pipedrive → Update a Person. Map the Person ID from the Watch Persons module ({{1.id}}). Then map the enriched data:

  • Emails → {{ifempty(2.datas[].contact.most_probable_email; "N/A")}}

  • Phones → {{ifempty(2.datas[].contact.most_probable_phone; "N/A")}}

The ifempty function ensures the field is set to "N/A" if FullEnrich doesn't find a result.

4. Test and activate

Click Run once to test, then create a new person in Pipedrive. Check that the Email and Phone fields have been updated. Once confirmed, toggle the scenario ON and set the polling schedule.

Problem

Solution

FullEnrich returns no email

Make sure First Name and Last Name are mapped correctly from the Watch Persons module. Adding the company domain improves match rates significantly.

Pipedrive update fails

Check that the Person ID is mapped from the Watch Persons module ({{1.id}}). Make sure the Emails and Phones fields are mapped as arrays.

Scenario doesn't trigger

Make sure the trigger is set to add_time and that new persons are being created after you activated the scenario.

Email/Phone shows "N/A"

This means FullEnrich couldn't find a result. Try adding more data (company domain, organization name) to improve match rates.

n8n

What this workflow does: When a new person is created in Pipedrive, the workflow sends the contact details to FullEnrich for enrichment, then updates the same Pipedrive person with verified email and phone. Uses two parallel flows because FullEnrich works asynchronously.

Top flow (2 nodes): Pipedrive Trigger (instant) → Start enrichment (FullEnrich)
Bottom flow (2 nodes): FullEnrich Callback → Update Pipedrive Person

1. Import the workflow

Click Copy Template URL above. In n8n, go to Workflows → Add Workflow → ⋯ (three-dot menu) → Import from URL and paste the URL.

2. Pipedrive Trigger (instant)

Open the Pipedrive Trigger node. Set the action to Create and the entity to Person. Connect your Pipedrive account. This node fires instantly via webhook when a new person is created in Pipedrive.

3. Start enrichment (FullEnrich)

Open the FullEnrich node. Connect your API key and map the fields:

  • Enrichment Name → Pipedrive

  • First Name → {{ $json.data.name }}

  • Last Name → {{ $json.data.last_name }}

  • Company Name → {{ $json.data.org_name }}

  • Webhook URL → production URL of the callback webhook (Step 4)

Add a Custom Field with key person id and value {{ $json.data.id }} — this passes the Pipedrive person ID through to the callback.

4. FullEnrich Callback (bottom flow)

Open the Webhook node (bottom flow). The HTTP method is set to POST and the path to fullenrich-callback. Copy this node's production URL and paste it in the FullEnrich node's Webhook URL field (Step 3).

5. Update Pipedrive Person

Open the Pipedrive node after the callback. The resource is set to Person and the operation to Update. Map the fields:

  • Person ID → {{ $json.body.datas[0].custom["person id"] }}

  • Email → {{ $json.body.datas[0].contact.most_probable_email }}

  • Phone → {{ $json.body.datas[0].contact.most_probable_phone }}

6. Test and activate

Click Test workflow, then create a new person in Pipedrive. The top flow sends the data to FullEnrich. After a few seconds, the callback webhook receives the enriched results and updates the person with email and phone. Toggle the workflow to Active and make sure the Webhook URL is set to the production URL.

Problem

Solution

Pipedrive trigger doesn't fire

Make sure the Pipedrive account is connected and the trigger is set to action Create, entity Person. Create a new person after activating the workflow.

FullEnrich returns no email

Make sure First Name (data.name) and Last Name (data.last_name) are mapped correctly. Adding the company name (data.org_name) improves match rates.

Callback webhook never receives data

Make sure you're using the production webhook URL (without webhook-test) and that the workflow is Active.

Pipedrive update fails

Check that custom["person id"] contains a valid Pipedrive person ID. Make sure the Pipedrive credentials have write access to Persons.