Power a CRM's native contact-enrichment button

Fill contact records with email and mobile inside the CRM or browser extension reps already use.

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

A selection of teams that run this job on Forager · plus other sales-tech platforms

Uses POST /person_detail_lookup/, POST /person_contacts_lookup/phone_numbers/ · Person enrichment API reference

What it costs: 15 credits per mobile found · 5 credits per email found. A mobile or email lookup that returns nothing costs 0 credits. Enrichment and search are charged per request: credit pricing.

How the data flows

2 inputs → Person enrichment + Mobile numbers + Work emails → 3 fields sample data

01 · Inputs

LinkedIn URL

linkedin.com/in/jane-example

CRM contact id

linkedin.com/in/jane-example

02 · Forager

Person enrichment + Mobile numbers + Work emails POST /person_detail_lookup/

Match found

03 · Outputs

Jane ExampleVP Revenue Operations · Example Inc.

work email: jane@example.com
phone number: +1 (415) 555-0142
role title: VP Revenue Operations
name: Jane Example
company: Example Inc.

3 fields in the responseexample data

Steps

Extension sends linkedin_public_identifier or email to the platform's waterfall
Resolve identity with POST /person_detail_lookup/
Return work email and mobile from /work_emails/ and POST /person_contacts_lookup/phone_numbers/
Write fields back to the CRM record with provider attribution

import json, os, requests

BASE = "https://api-v2.forager.ai/api/{account_id}/datastorage"
HEADERS = {"X-API-KEY": os.environ["FORAGER_KEY"]}
body = json.load(open("request.json"))  # request fields: see the API reference

# 1. Extension sends linkedin_public_identifier or email to the platform's
# waterfall

# 2. Resolve identity with POST /person_detail_lookup/
r1 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body)

# 3. Return work email and mobile from /work_emails/ and POST
# /person_contacts_lookup/phone_numbers/
r2 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)

# 4. Write fields back to the CRM record with provider attribution

# 1. POST /person_detail_lookup/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_detail_lookup/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

# 2. POST /person_contacts_lookup/phone_numbers/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/phone_numbers/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Generated from the recipe stepsRequest fields: API reference

Run it yourself: Person enrichment API reference

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Inputs and outputs

Inputs	Outputs
LinkedIn URL	`work_email`
CRM contact id	`phone_number`
	`role_title`

Questions about this recipe

How do CRM extensions find emails and phone numbers for contacts?

Return work email and mobile from /work_emails/ and POST /person_contacts_lookup/phone_numbers/. Write fields back to the CRM record with provider attribution.

What does it cost to power a CRM's native contact-enrichment button?

Person enrichment: 1 credit per request, charged whether or not data comes back. Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. Growth's 8,250 monthly credits cover 550 mobiles, 1,650 emails or 8,250 person enrichments, or a mix. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

What do I need to run this recipe, and what comes back?

You send CRM contact id and LinkedIn URL. You get back phone_number, role_title and work_email, as JSON. You also need a Forager API key, which comes with a free account.

Which data API can power an 'enrich' button in my CRM product?

You send LinkedIn URL and CRM contact id. You get back work_email, phone_number and role_title. CRM end users get filled contact records inside the tool they already use.

Is there a free way to try Forager on this workflow?

Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.

When should I run this workflow?

When a rep clicks 'enrich' on a CRM contact or a profile page. CRM end users get filled contact records inside the tool they already use.

Which Forager products does this recipe use?

Person enrichment, mobile numbers and work emails. Person enrichment: a full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you.

How do I know the data is right?

Forager ranked #1 of 10 in Clay's 2026 test of mobile data providers, by quality score: Clay's measure of how likely a dialled number reaches the right person. The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.

How do I enrich HubSpot contacts with mobile numbers?

Extension sends linkedin_public_identifier or email to the platform's waterfall. Return work email and mobile from /work_emails/ and POST /person_contacts_lookup/phone_numbers/.

Which tools can run this workflow?

Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Or call the endpoints in the steps above from your own code with one API key.

How many steps is this workflow?

4 steps: extension sends linkedin_public_identifier or email to the platform's waterfall, resolve identity with POST /person_detail_lookup/, return work email and mobile from /work_emails/ and POST /person_contacts_lookup/phone_numbers/ and write fields back to the CRM record with provider attribution.

Is there a contract or minimum commitment?

No contract to start: a free account comes with $5 in credits. To keep using Forager, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.

A selection of teams that run this job on Forager · plus other sales-tech platforms

Clay
- GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
Juicebox
- AI candidate sourcing
Selected use case: Forager data behind its PeopleGPT search and sourcing agents.
Nooks
- Power & parallel dialers
Selected use case: mobile numbers inside their dialer.
Monaco
- CRM add-ons
Selected use case: mobile data in its enrichment waterfall.
Amplemarket
- AI SDRs
Selected use case: mobile numbers inside its contact waterfall.
HubSpot
- CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
Myko AI
- CRM add-ons
Voice-first tool that lets field reps update Salesforce, Veeva and Dynamics.
item
- CRM add-ons
AI-native CRM where teams and agents work side by side.

Power a CRM's native contact-enrichment button

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How do CRM extensions find emails and phone numbers for contacts?

What does it cost to power a CRM's native contact-enrichment button?

What do I need to run this recipe, and what comes back?

Which data API can power an 'enrich' button in my CRM product?

Is there a free way to try Forager on this workflow?

When should I run this workflow?

Which Forager products does this recipe use?

How do I know the data is right?

How do I enrich HubSpot contacts with mobile numbers?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

More recipes for CRM add-ons

Detect CRM contacts who changed jobs and alert on moved champions

Pre-build each new customer's TAM on day one inside an AI-native CRM

Alert account owners when a customer posts a job naming a competitor

Keep one canonical company record per account in a CRM add-on

Merge CRM duplicates that use a personal and a work email

Add a mobile-number slot to a multi-provider enrichment waterfall

Put people, company and job data your users can act on inside your product