CRMs
Check phone numbers, carriers and phone complaints in Pipedrive
Validate the phone numbers on Pipedrive persons when a deal or person changes, and write the formatted number and its type back to the person.
Why the data matters in Pipedrive
Pipedrive reps work deals in a pipeline view and call from the person attached to each deal. A number with a missing country code or a toll-free line sitting in the main phone slot stalls a deal quietly, because the stage keeps its date while the rep cannot reach anyone.
What LookValid checks
| Product | What it does here | Credits |
|---|---|---|
| Phone Numbering-Plan Validation | Returns E.164, national and international formats, the country and the type the numbering plan assigns. It cannot say whether the line is active. | 1 credit per valid number |
| Carrier Lookup (original carrier) | Returns the carrier originally assigned a US number block, with the rate center and state. Ported numbers still show the first carrier. | 1 credit per lookup (numbers outside the covered numbering plan areas are free) |
| Phone Spam Check | Returns the number of consumer complaints on record for a number, to review a person whose number others report. | 1 credit per number with complaints on record |
| IP Intelligence | Locates the IP address of a web form submission by country, region and network, which helps compare it with the country a lead typed. | 1 credit per lookup |
Connect it in four steps
- Register at LookValid and add a key from the dashboard's API keys screen.
- In Pipedrive a global admin creates the automation webhook with your function endpoint and any credentials it needs, and the LookValid key stays in the LOOKVALID_API_KEY variable of the host that runs the function.
- In the automation choose the webhook, send the person phone in a raw JSON body, and have the function post it to the phone endpoint, treating found:false as a person to leave unchanged and any error as a failed run to inspect in the execution history.
- Have the function call PATCH /api/v2/persons/{id}, sending Phone valid, Phone E.164 and Phone type inside the custom_fields object, where each field is keyed by its 40-character hash from the field settings rather than its label.
A Node function behind the endpoint URL that a Pipedrive automation webhook action calls when a person is added or a phone changes. The call is POST https://YOUR_API_HOST/v1/phone and costs 1 credit per valid number.
const API_URL = "https://YOUR_API_HOST/v1/phone";
export async function validatePipedrivePhone(value) {
const response = await fetch(API_URL, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOKVALID_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"phone": value,
}),
});
const result = await response.json();
if (!response.ok) throw new Error(`${result.error.code}: ${result.error.fix}`);
if (!result.found) return null;
return {
"Phone valid": result.data?.valid ?? null,
"Phone E.164": result.data?.e164 ?? null,
"Phone type": result.data?.number_type ?? null,
};
}
| Response field | Goes into |
|---|---|
| data.valid | Phone valid |
| data.e164 | Phone E.164 |
| data.number_type | Phone type |
The recipe returns nothing when the lookup finds nothing, which costs no credits for this product, and stops with the error code and fix on a failed request.
Without code
The same flow works without hosting a function. Use an automation platform with a generic HTTP request step, no dedicated app needed: trigger on a new person in Pipedrive, send the phone to the LookValid phone endpoint in the HTTP step, and add a step that updates the person custom field with the returned type.
Questions
What does a Pipedrive lookup cost in credits?
The phone product rate on the pricing page, once per number checked.
What does the phone check leave out?
It reads numbering-plan rules only, so it cannot say if the number is connected, ported or who owns it.
Does the automation webhook need a plan upgrade?
Pipedrive states the automation webhook action requires an Advanced or higher plan and an admin to create it. Check your plan before building the flow.
Sources
- Pipedrive Knowledge Base, automations webhook requests https://support.pipedrive.com/en/article/automations-webhook-requests, read 2026-10-18
- Pipedrive API reference, Persons (update a person) https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson, read 2026-10-18
- LookValid API reference: Phone Numbering-Plan Validation https://lookvalid.com/docs/api/phone, read 2026-10-18
LookValid is run by Meralume Labs. It is not connected to, endorsed by or a partner of any company or product named on this page, and every product name belongs to its owner.
Related pages
LookValid bills every lookup in credits from one shared balance, so the same key works for each check above.
See Phone Numbering-Plan Validation