How ProfileSpider Email Finding Works
Learn how ProfileSpider email finding works, when it uses credits, what inputs help, and what happens when no valid email is found.
Quick answer
ProfileSpider email finding helps find valid business emails for saved rows. Person email finding uses 3 credits per verified email returned. Company email finding uses 3 credits per call if at least one valid email is returned, up to 20 emails. If no valid email is returned, there is no charge.
Overview
What Email Finding Does
Email finding helps add valid email addresses to saved ProfileSpider rows.
Person email finding
Finds a verified person email for a saved row when enough person and company context is available.
Company email finding
Finds valid company emails for a company or domain, up to 20 emails in one successful call.
Valid results only
Email finding charges only when a valid result is returned. No valid result means no charge.
Works from saved rows
Email finding is used from saved ProfileSpider rows, after extraction and review.
Export afterwards
After email finding, you can export the updated list to CSV, Excel, or JSON.
Not guaranteed
Not every person or company has a discoverable valid email. Email finding is an enrichment step, not a guarantee.
Person emails
Person Email Finding
Use this when you want a business email for a specific person.
Best inputs
Person email finding works best when the row includes a full name, company, company domain, and profile URL such as LinkedIn.
Credit rule
A verified person email uses 3 credits. If no valid email is returned, there is no charge.
LinkedIn context can help
A LinkedIn profile URL can help provide context when it is available in the saved row.
Company context matters
A company name and domain usually improve the chance of finding the right business email.
Company emails
Company Email Finding
Use this when you want company-level emails from a business or domain.
Company-level search
Company email finding looks for valid emails connected to a company or domain.
Up to 20 emails
A successful company email-finding call can return up to 20 valid emails.
Credit rule
Company email finding uses a flat 3 credits if at least one valid email is returned.
No valid result = no charge
If no valid company email is returned, there is no charge.
Inputs
What Inputs Help Email Finding
Better input data improves the chance of a useful result.
Full person name.
Company name.
Company website or domain.
LinkedIn profile URL when available.
Profile URL or source URL for context.
Clear role or title when available.
A clean saved row with irrelevant or duplicated data removed.
Credits
How Email Finding Uses Credits
Email finding is charged only when a valid result is returned.
Verified person email
3 credits per verified person email returned.
Company emails
3 credits per company email-finding call when at least one valid email is returned, up to 20 emails.
No valid result
If no valid email is returned, there is no charge.
Export is free
Exporting rows after email finding does not use credits.
Tags and notes are free
Adding tags or notes before or after email finding uses 0 credits.
Page scrape is separate
The original page scrape uses 1 credit per page. Email finding is a separate credit-using action.
Limits
What Email Finding Is Not
Email finding does not guarantee that every row will return an email.
Email finding is not the same as extracting emails already visible on a page.
Email finding is not the same as enrichment. Enrichment opens URLs to add more row details.
Email finding is not currently a bulk list-wide workflow.
Email finding should not replace manual review for high-value outreach.
Email finding does not remove your responsibility to follow applicable outreach, privacy, and data-use rules.
Workflow
Email Finding Is Currently Per Row
ProfileSpider email finding is currently a per-row workflow.
That means you choose the saved row where email finding is useful, run the email-finding action, and review the result.
Do not plan workflows around bulk email finding until that feature is available in the product.
Steps
How to Find an Email from a Saved Row
Start with a saved row that has enough person or company context.
1. Extract a source page
Run ProfileSpider on a page with people, companies, profiles, or leads.
2. Save useful rows
Save the extracted rows to a list so you can review them before email finding.
3. Review the row
Check that the row has enough context, such as name, company, domain, and profile URL.
4. Run email finding
Run email finding on the row where an email address is needed and appropriate.
5. Review the result
If a valid email is returned, it is added to the row and credits are charged according to the email-finding rule.
6. Export
Export the updated list to CSV, Excel, or JSON when it is ready.
Examples
Email Finding Examples
Common cases so you can understand credit use.
One verified person email
If person email finding returns one verified email, it uses 3 credits.
No person email found
If no valid person email is returned, it uses 0 credits.
Company emails found
If company email finding returns at least one valid email, the call uses 3 credits, up to 20 emails.
No company emails found
If no valid company email is returned, it uses 0 credits.
Export after email finding
Exporting the list after emails are found uses 0 credits.
Mark rows for review
Adding tags like needs-email, email-found, or no-email-found uses 0 credits.
Timing
When to Use Email Finding
Use email finding after extraction and review, not before cleaning the list.
Use email finding after saving rows to a list.
Use email finding after removing obviously irrelevant rows.
Use email finding when the row has a clear person, company, and domain context.
Use email finding before export if the final list needs emails.
Skip email finding for rows that are not relevant enough to contact.
Use tags or notes to mark rows that still need email review.
Visible emails
Visible Emails vs Email Finding
If an email address is visible on the source page, ProfileSpider can include it in the extracted row.
Email finding is different. It is a separate action used when the row does not already contain a useful email and you want ProfileSpider to look for one.
Visible email extraction happens as part of page extraction. Email finding has its own credit rule and only charges when a valid result is returned.
Best practices
Best Practices for Email Finding
Clean the list before running email finding.
Prioritize rows with clear name, company, and domain context.
Use tags such as needs-email, email-found, or no-email-found to track status.
Keep source URLs so you can verify where each lead came from.
Review returned emails before outreach.
Follow the rules that apply to your market, use case, and outreach workflow.
Storage
Storage and Privacy
Saved profiles, lists, tags, and notes are stored locally in your browser.
Email finding uses backend or provider services because ProfileSpider has to search for and validate email results.
After a valid email is returned and saved to a row, that row remains part of your local ProfileSpider list. Export important lists if you want a backup.
Troubleshooting
Common Email Finding Issues
No email found
Some people or companies do not have a discoverable valid email. No valid result means no charge.
Missing company domain
Email finding usually works better with a company domain. Add or enrich the company website first where useful.
Unclear person identity
Rows with incomplete names, unclear company context, or wrong profile URLs may be harder to match.
Too many low-quality rows
Review the list before email finding so you do not spend time on irrelevant rows.
Questions