Brief users on the people they are about to meet, from an email address

Let a meeting-prep or calendar product brief its user on who they are about to meet or email: role, employer, career history and company context.

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

Uses POST /person_detail_reverse_lookup/by_email/, POST /person_detail_lookup/, POST /organization_search/ · Reverse email lookup API reference

What it costs: Charged per request: credit pricing.

How the data flows

3 inputs → Reverse email lookup + Person enrichment + Company enrichment → 4 fields sample data

01 · Inputs

Work email

kim@example.com

calendar attendee

linkedin.com/in/kim-exemplar

Company

Example Inc.

02 · Forager

Reverse email lookup + Person enrichment + Company enrichment POST /person_detail_reverse_lookup/by_email/

Match found

03 · Outputs

Kim ExemplarVP Revenue Operations · Example Inc.

person profile: /in/kim-exemplar
role title: VP Revenue Operations
employer: Example Inc.
name: Kim Exemplar
mobile: +1 (416) 555-0186
work email: kim@example.com

4 fields in the responseexample data

Steps

Resolve each new email address with POST /person_detail_reverse_lookup/by_email/
Pull full career history with POST /person_detail_lookup/
Add company context (industry, size, location) with POST /organization_search/
Write a short pre-meeting brief in your product and cache it against the contact

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. Resolve each new email address with POST
# /person_detail_reverse_lookup/by_email/
r1 = requests.post(f"{BASE}/person_detail_reverse_lookup/by_email/", headers=HEADERS, json=body)

# 2. Pull full career history with POST /person_detail_lookup/
r2 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body)

# 3. Add company context (industry, size, location) with POST
# /organization_search/
r3 = requests.post(f"{BASE}/organization_search/", headers=HEADERS, json=body)

# 4. Write a short pre-meeting brief in your product and cache it against
# the contact

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

# 2. 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

# 3. POST /organization_search/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/organization_search/ \
  -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: Reverse email lookup 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
email address	`person profile`
calendar attendee	`role_title`
name + company	`employer`
	`company summary`

Questions about this recipe

How can a meeting-prep app know who I'm meeting from just their email address?

Resolve each new email address with POST /person_detail_reverse_lookup/by_email/. Write a short pre-meeting brief in your product and cache it against the contact.

What does it cost to brief users on the people they are about to meet, from an email address?

Reverse email lookup: 5 credits per request, charged whether or not data comes back. Person enrichment: 1 credit per request, charged whether or not data comes back. Company enrichment: 1 credit per request, charged whether or not data comes back. Growth's 8,250 monthly credits cover 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 calendar attendee, email address and name + company. You get back company summary, employer, person profile and role_title, as JSON. You also need a Forager API key, which comes with a free account.

Which API returns someone's job title and company from an email?

This recipe uses Forager Reverse email lookup, Person enrichment and Company enrichment. Reverse email lookup: Turn an email address into a full person profile: name, title, company, location and social links. Let a meeting-prep or calendar product brief its user on who they are about to meet or email: role, employer, career history and company context.

Can I test reverse email lookup 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?

When a calendar invite, new email thread or new contact appears in the user's account. Users walk into meetings knowing who they are talking to without manual research.

Which Forager products does this recipe use?

Reverse email lookup, person enrichment and company enrichment. Reverse email lookup: turn an email address into a full person profile: name, title, company, location and social links. Person enrichment: a full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels.

How accurate is Forager data?

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 calendar attendees with job title?

Resolve each new email address with POST /person_detail_reverse_lookup/by_email/. Pull full career history with POST /person_detail_lookup/.

Which tools can run this workflow?

Native in Clay, 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: resolve each new email address with POST /person_detail_reverse_lookup/by_email/, pull full career history with POST /person_detail_lookup/, add company context (industry, size, location) with POST /organization_search/ and write a short pre-meeting brief in your product and cache it against the contact.

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.

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.
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.
Freckle
- GTM workflow builders
Selected use case: Forager as a selectable mobile number provider in its waterfalls.

Sources

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

Brief users on the people they are about to meet, from an email address

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How can a meeting-prep app know who I'm meeting from just their email address?

What does it cost to brief users on the people they are about to meet, from an email address?

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

Which API returns someone's job title and company from an email?

Can I test reverse email lookup for free?

When should I run this workflow?

Which Forager products does this recipe use?

How accurate is Forager data?

How do I enrich calendar attendees with job title?

Which tools can run this workflow?

How many steps is this workflow?

Do I need a subscription?

More recipes for LLM apps

License a people feed for retrieval over people and company records

Ground AI CRM agents with fresh company and people records

Refresh contact data before an agent writes to the CRM

Resolve a sign-up email to a person inside a copilot

Answer hiring and labor-market questions in an AI analyst from a job postings feed

Train title-normalisation and company-matching models on structured profiles

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