Add Forager as a waterfall step in an agent's contact tool

Give an agent framework or GTM agent a contact-lookup tool that tries sources in order and returns the first verified result, with Forager as the mobile and email step.

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 teams on Forager

Tools named: LinkedIn

Uses POST /person_contacts_lookup/phone_numbers/, POST /person_contacts_lookup/work_emails/ · Mobile numbers 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.

How the data flows

2 inputs → Mobile numbers + Work emails + Personal emails → 5 fields sample data

01 · Inputs

LinkedIn URL

linkedin.com/in/kim-exemplar

Company domain

example.com

02 · Forager

Mobile numbers + Work emails + Personal emails POST /person_contacts_lookup/phone_numbers/

Match found Pay per field · Empty result: 0 credits

03 · Outputs

Kim ExemplarVP Revenue Operations · Example Inc.

phone number: +1 (416) 555-0186
work email: kim@example.com
personal email: kim.e@example.net
source: forager
person id: per_8f3a1c
name: Kim Exemplar

5 fields in the responseexample data

Steps

Define one find_contact tool in your framework that takes a LinkedIn URL or name and company
Inside it, call POST /person_contacts_lookup/phone_numbers/ then POST /person_contacts_lookup/work_emails/ when the earlier source returns nothing
Return a typed result with the field names, the source that found it and the person_id
Count credits per found result only, so a miss in the Forager step adds 0 to the run's cost

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. Define one find_contact tool in your framework that takes a LinkedIn
# URL or name and company

# 2. Inside it, call POST /person_contacts_lookup/phone_numbers/ then POST
# /person_contacts_lookup/work_emails/ when the earlier source returns
# nothing
r1 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)
r2 = requests.post(f"{BASE}/person_contacts_lookup/work_emails/", headers=HEADERS, json=body)

# 3. Return a typed result with the field names, the source that found it
# and the person_id

# 4. Count credits per found result only, so a miss in the Forager step adds
# 0 to the run's cost

# 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

# 2. POST /person_contacts_lookup/work_emails/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/work_emails/ \
  -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 URL or public identifier	`phone_number`
full name + company domain	`work_email`
	`personal_email`
	`source`
	`person_id`

Questions about this recipe

How do I add a contact waterfall to my agent's tools?

Define one find_contact tool in your framework that takes a LinkedIn URL or name and company. Inside it, call POST /person_contacts_lookup/phone_numbers/ then POST /person_contacts_lookup/work_emails/ when the earlier source returns nothing.

What does it cost to add Forager as a waterfall step in an agent's contact tool?

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. Personal emails: 5 credits per personal email found, and a personal email lookup that finds nothing costs 0 credits. Growth's 8,250 monthly credits cover 550 mobiles or 1,650 emails, 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 full name + company domain and LinkedIn URL or public identifier. You get back person_id, personal_email, phone_number and source, as JSON. You also need a Forager API key, which comes with a free account.

Which contact data API can be one step in an agent's lookup tool?

This recipe uses Forager Mobile numbers, Work emails and Personal emails. Mobile numbers: Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Give an agent framework or GTM agent a contact-lookup tool that tries sources in order and returns the first verified result, with Forager as the mobile and email step.

Can I test mobile numbers for free?

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?

An agent's find-contact tool returns nothing for a third of prospects because its single source has no mobiles. The agent's tool fills the contacts its first source missed, and the platform sees the hit rate of each step in its own logs.

Which Forager products does this recipe use?

Mobile numbers, work emails and personal emails. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Work emails: verified work email addresses for a person at their current employer.

How accurate is Forager data?

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: define one find_contact tool in your framework that takes a LinkedIn URL or name and company, inside it, call POST /person_contacts_lookup/phone_numbers/ then POST /person_contacts_lookup/work_emails/ when the earlier source returns nothing, return a typed result with the field names, the source that found it and the person_id and count credits per found result only, so a miss in the Forager step adds 0 to the run's cost.

Do I need a subscription?

Not to test: 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 our users see Forager data in 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 teams on Forager

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.
Emergent Labs
- Agent builders
AI app-building platform where agents design, code and deploy full-stack apps.
Airscale
- Waterfall enrichment
Selected use case: a Forager step in its mobile number waterfall.
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.
Freckle
- GTM workflow builders
Selected use case: Forager as a selectable mobile number provider in its waterfalls.

Add Forager as a waterfall step in an agent's contact tool

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How do I add a contact waterfall to my agent's tools?

What does it cost to add Forager as a waterfall step in an agent's contact tool?

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

Which contact data API can be one step in an agent's lookup tool?

Can I test mobile numbers for free?

When should I run this workflow?

Which Forager products does this recipe use?

How accurate is Forager data?

Which tools can run this workflow?

How many steps is this workflow?

Do I need a subscription?

Can our users see Forager data in our product?

More recipes for agent builders

Give coding agents typed people and company data tools

Offer people and company data as a built-in integration in an AI app builder

Ground an agent's account research with company enrichment

Offer people search as an agent tool

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

Back a sales-intelligence database with an additional mobile source

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