“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.
Open Deepline's Forager guide, connect Forager the way it describes, and use the Forager step for work emails. The guide is linked from this page.
What do work emails cost for Deepline users?
⌄
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. How Deepline bills for its own steps is set by Deepline. See plans and prices
How do Deepline users use Forager work emails?
⌄
Raise mobile and contact coverage inside a contact-data product by blending a complementary source behind existing data. Verified work email addresses for a person at their current employer. This page walks through 3 workflows with the exact steps.
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.
Can Deepline users test work emails 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.
What inputs does it take and what does it return?
⌄
You send regions, persona titles and company filters. You get back work_email, phone_number, role_title and personal_email, from POST /person_contacts_lookup/work_emails/, as JSON.
How do I know the data is right?
⌄
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.
Who built and maintains the Deepline integration?
⌄
Partner-built. The partner built and maintains the Forager connection. Questions about the Deepline side go to Deepline; questions about Forager data come to us.
How can I add contact enrichment to my SaaS product without managing many vendors?
⌄
Call the embedded waterfall from the product's backend with linkedin_public_identifier or name + domain. Use /person_contacts_lookup/work_emails/ and /phone_numbers/ as steps with validation.
Can I use the Forager API directly instead of Deepline?
⌄
Yes. The same data is available through the REST API with one API key, so you can call it from your own code or another tool. Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code.
Do I need a subscription?
⌄
Not to test: a free account comes with $5 in credits. To keep using work emails, 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.
How is the data sourced, and what about privacy?
⌄
Bring your legal and security questions to a call with our team, and we take you through how Forager data is sourced and the terms that cover work emails for Deepline users. Forager's privacy policy is public, and anyone can send a request about their own personal data through the consumer rights form on forager.ai.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.