Add a pay-per-find phone finder to multichannel sales sequences

Let a sequencing platform add call steps by finding mobiles for the leads already in a campaign.

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

Your list

contacts.csv · 1,200 rows

LinkedIn URL

linkedin.com/in/lee-sampler

02 · Forager

Mobile numbers POST /person_contacts_lookup/phone_numbers/

Match found Pay per field · Empty result: 0 credits

03 · Outputs

Lee SamplerVP Revenue Operations · Example Inc.

phone number: +1 (312) 555-0107
name: Lee Sampler
title: VP Revenue Operations
work email: lee@example.com
company: Example Inc.

2 fields in the responseexample data

Steps

Collect leads in the sequence lacking phone
Query POST /person_contacts_lookup/phone_numbers/ with linkedin_public_identifier inside the platform's phone-finder waterfall
Write phone_number to the lead and unlock the call or SMS step
Bill the user's credits only on found numbers and show per-provider find rate

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. Collect leads in the sequence lacking phone

# 2. Query POST /person_contacts_lookup/phone_numbers/ with
# linkedin_public_identifier inside the platform's phone-finder waterfall
r1 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)

# 3. Write phone_number to the lead and unlock the call or SMS step

# 4. Bill the user's credits only on found numbers and show per-provider
# find rate

# 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
campaign lead list	`phone_number`
LinkedIn URL	`tier`
	`credits charged`

Questions about this recipe

How do I find phone numbers for leads already in my email sequence?

Collect leads in the sequence lacking phone. Query POST /person_contacts_lookup/phone_numbers/ with linkedin_public_identifier inside the platform's phone-finder waterfall.

What does it cost to add a pay-per-find phone finder to multichannel sales sequences?

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 campaign lead list and LinkedIn URL. 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 phone finder works inside sales engagement platforms?

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. Let a sequencing platform add call steps by finding mobiles for the leads already in a campaign.

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 adds a call step to a multichannel email sequence and leads lack phone numbers. Sales teams add phone touches to sequences and book more meetings per SDR with fewer dials.

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 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 add calling step to email sequence find mobile?

Collect leads in the sequence lacking phone. Write phone_number to the lead and unlock the call or SMS step.

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: collect leads in the sequence lacking phone, query POST /person_contacts_lookup/phone_numbers/ with linkedin_public_identifier inside the platform's phone-finder waterfall, write phone_number to the lead and unlock the call or SMS step and bill the user's credits only on found numbers and show per-provider find rate.

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.
Stamina
- Sales engagement
AI outbound sales platform for small businesses.
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.
Airscale
- Waterfall enrichment
Selected use case: a Forager step in its mobile number waterfall.
FirstTouch
- Sales engagement
LinkedIn outreach and social-selling platform that works from HubSpot, AI agents and its API.

Add a pay-per-find phone finder to multichannel sales sequences

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How do I find phone numbers for leads already in my email sequence?

What does it cost to add a pay-per-find phone finder to multichannel sales sequences?

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

Which phone finder works inside sales engagement platforms?

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 add calling step to email sequence find mobile?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

More recipes for sales engagement

Bulk-enrich a target-account CSV before an SDR sprint

Enrich lead list exports with email and mobile in one click

Reach CISOs and IT security leaders by direct phone

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

Back a sales-intelligence database with an additional mobile source

Offer mobile and email enrichment as native actions in a GTM workflow builder

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