Add a premium phone reveal to a credit-based prospecting tool

Offer a 'reveal phone' action priced in credits so SMB reps and consultants can call executives after reading an account brief.

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_contacts_lookup/phone_numbers/ · Mobile numbers API reference

What it costs: 15 credits per mobile found. A mobile or email lookup that returns nothing costs 0 credits.

Mobile numbers
API
Waterfall slot
Sales tech

How the data flows

2 inputs → Mobile numbers → 3 fields sample data

01 · Inputs

LinkedIn URL

linkedin.com/in/priya-fixture

user credit balance

linkedin.com/in/priya-fixture

02 · Forager

Mobile numbers POST /person_contacts_lookup/phone_numbers/

Match found Pay per field · Empty result: 0 credits

03 · Outputs

Priya FixtureVP Revenue Operations · Example Inc.

phone number: +44 20 7946 0958
name: Priya Fixture
title: VP Revenue Operations
work email: priya@example.com
company: Example Inc.

2 fields in the responseexample data

Steps

Call POST /person_contacts_lookup/phone_numbers/ on reveal with linkedin_public_identifier
Charge the user's credits only when a number returns
Show tier (Gold or Silver) and store the number on the prospect
Track reveal-to-call conversion

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. Call POST /person_contacts_lookup/phone_numbers/ on reveal with
# linkedin_public_identifier
r1 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)

# 2. Charge the user's credits only when a number returns

# 3. Show tier (Gold or Silver) and store the number on the prospect

# 4. Track reveal-to-call conversion

# 1. 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: Mobile numbers 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 identifier	`phone_number`
user credit balance	`tier`
	`credits charged`

Questions about this recipe

How do prospecting Chrome extensions find phone numbers?

Call POST /person_contacts_lookup/phone_numbers/ on reveal with linkedin_public_identifier. Charge the user's credits only when a number returns.

What does it cost to add a premium phone reveal to a credit-based prospecting tool?

Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Growth's 8,250 monthly credits cover 550 mobiles, 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 LinkedIn identifier and user credit balance. You get back credits charged, phone_number and tier, as JSON. You also need a Forager API key, which comes with a free account.

Which mobile number API works for pay-per-reveal pricing?

This recipe uses Forager Mobile numbers. Mobile numbers: Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Offer a 'reveal phone' action priced in credits so SMB reps and consultants can call executives after reading an account brief.

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 user clicks reveal phone on a prospect in a Chrome extension or account brief. SMB reps get dial-ready numbers without paying for multiple tools.

Which Forager products does this recipe use?

Mobile numbers. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you.

How do you check data quality?

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.

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: call POST /person_contacts_lookup/phone_numbers/ on reveal with linkedin_public_identifier, charge the user's credits only when a number returns, show tier (Gold or Silver) and store the number on the prospect and track reveal-to-call conversion.

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.

Can we show Forager data inside our product?

Yes, under platform terms. Self-serve plans cover internal use by your own team. Showing Forager contacts to your users, or passing records on, is licensed separately: talk to sales about volume and which fields your users need to see.

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.
Airscale
- Waterfall enrichment
Selected use case: a Forager step in its mobile number waterfall.
Deepline
- Waterfall enrichment
Selected use case: Forager lookups as typed tools inside enrichment waterfalls.

19 typed Forager tools available inside Deepline¹
HubSpot
- CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
BetterContact
- Waterfall enrichment
Selected use case: a Forager step in its waterfall for mobile numbers.
Jeeva AI
- AI SDRs
Agentic platform of AI digital workers for sales teams.

Sources

¹ Deepline: deepline.com/integrations/forager (public page, read 2026-10-21).

Add a premium phone reveal to a credit-based prospecting tool

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How do prospecting Chrome extensions find phone numbers?

What does it cost to add a premium phone reveal to a credit-based prospecting tool?

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

Which mobile number API works for pay-per-reveal pricing?

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 you check data quality?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

Can we show Forager data inside our product?

More recipes for waterfall enrichment

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

Convert personal-email sign-ups into work identities

Revive a dead CRM with a one-time contact refresh

Embed a validated email and mobile waterfall inside a SaaS product

Enrich and route inbound demo requests in real time

Enrich scanned event badges into CRM-ready leads

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