Who evaluates work emails at spreadsheet/agentic GTM workflow builders, and what they are judged on
Product manager who owns the enrichment feature: judged on what users see when they open a record
Engineering lead integrating the API: judged on response time and errors they can route on
Partnerships or data lead managing vendors: judged on cost per valid result
A selection of GTM workflow builders using Forager for work emails · plus other sales-tech platformsSelected teams using Forager for work emails
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.
Bitscale
GTM workflow builders
Selected use case: Forager in its contact waterfall for mobile numbers.
Scalestack
GTM workflow builders
Context and data infrastructure for enterprise GTM agents.
HubSpot
CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
Cargo
GTM workflow builders
Selected use case: enrichment plays that use Forager from its integrations catalog.
OXYGEN
GTM workflow builders
Agentic GTM platform with a multi-provider enrichment waterfall.
“We use Forager to enrich our contact data with email addresses and mobile phone numbers. After analyzing all the data providers we use, we found Forager to deliver the best overall data quality.”
AndelaRyley L.Growth Marketing Associate
800M+people
65M+companies
How to test it
Test work emails on your own sample
Pull a sample. Take profiles your users looked up last week.
Run it. Use a self-serve key, or book a demo and send us the list.
Measure what your users feel. Connect rate for mobiles, bounces for emails, and whether the right person answers.
How do GTM workflow builders use Forager work emails?
⌄
Give GTM engineers a mobile, email and person provider they can drop into any table, workflow or waterfall step, billed in platform credits. Verified work email addresses for a person at their current employer. This page walks through 3 workflows with the exact steps.
What do work emails cost for GTM workflow builders?
⌄
Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. That is $0.07 per work email on Starter month to month and $0.05 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
Why do GTM workflow builders add work emails?
⌄
Give your workflow users a contact step that connects. Products like yours are judged on connect rate and cost per valid result, which is why the cost that counts is per result that reaches the right person. Run your own sample to see what work emails returns for your users before you build on it.
How do I add mobile number provider to GTM workflow builder?
⌄
Expose person_detail_lookup, work_emails, personal_emails, phone_numbers and organization_search as native actions with field mapping. Let users chain the actions as waterfall steps after or before other providers.
What do I send, and what comes back?
⌄
You send persona titles, LinkedIn URL and account domain. You get back work_email, phone_number, role_title and person name, from POST /person_contacts_lookup/work_emails/, as JSON.
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.
Am I charged when no work email is found?
⌄
No. A work email lookup that finds nothing costs 0 credits, so you pay for work emails we find. Search, enrichment and reverse lookups are the exception: they are charged per request.
Is there a free way to try Forager?
⌄
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.
How can an insurtech find and contact independent insurance agency owners?
⌄
Find agencies with POST /organization_search/ (industries = insurance, employees_end small, locations). Identify principals/owners and agency managers with POST /person_role_search/.
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 is a work email finder different from guessing the email pattern?
⌄
A pattern guess (first.last@company.com) gives you an address that may not exist or may belong to someone who left. A work email lookup returns the address for that person at their current employer, and with Forager a work email lookup that finds nothing costs 0 credits.
Does Forager integrate with the tools we already use?
⌄
Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Everything else connects through the REST API with one API key.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
