Icypeas
Sales IntelligenceFind and verify emails and pull B2B lead data through Icypeas, with async single and bulk searches and a searchable people database. Agents build a verified list without a manual export cycle.
What This Integration Enables
Icypeas is built for volume, and the two things that make volume survivable are both here. The first is free sizing. Count People and Count Companies return how many records match a filter query without returning the records, and Icypeas charges nothing for them, so an agent can iterate on an ideal customer profile until the number is right before a single credit moves. The second is that bulk work is genuinely asynchronous at scale: Submit Bulk Search accepts up to 5000 rows for email search, verification or domain search in one named file, and Get Bulk Files reports what happened to that file in detail rather than as a status word.
That detail is the part worth designing around. Get Bulk Files returns how many rows are done, how many emails were found, how many were aborted and how many hit insufficient credits, plus a breakdown of result certainties. A 5000 row file can reach a terminal state having quietly skipped a slice of itself, and downstream that partial list looks exactly like a complete one. Reading those counts is the difference between an agent that reports a finished job and an agent that reports a finished job with 600 rows never attempted. Single searches follow the same submit-and-poll contract: Submit Email Search, Submit Email Verification and Submit Domain Search each return a search ID, and Get Search Results is polled until the status leaves NONE, SCHEDULED and IN_PROGRESS. Certainty comes back as ultra_sure, very_sure, probable or undeliverable, which is a more useful vocabulary than a score because each band maps to a different decision. Alongside the search surface, Icypeas exposes a searchable leads database and a set of synchronous profile operations, so an agent can resolve profile URLs, scrape up to 50 of them in one request, and run reverse email lookups in batches.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Sizing an audience before buying it
A campaign starts with a hypothesis about who to target. The agent calls Count People with the proposed filters covering job titles, seniority, location, skills and company attributes, and gets a number back for free. If the audience is too broad it tightens the filters and counts again. If it is too narrow it relaxes them. Only when the count is right does it call Find People to pull the profiles and export them to Google Sheets for review. Count Companies does the same job on the account side, validating an ideal customer profile before Find Companies spends anything on it.
A 5000 row file processed and then actually checked
An imported list needs email resolution at scale. The agent calls Submit Bulk Search with the rows populated for the chosen task, then polls Get Bulk Files. Rather than waiting for a single completion flag, it reads the full breakdown: rows done, emails found, rows aborted, rows that hit insufficient credits, and the certainty distribution across the results. It writes the ultra_sure and very_sure results into Smartlead as the campaign list, holds the probable band, and reports the aborted and out-of-credit counts as an unresolved remainder rather than folding them into the total.
Turning bare profile links into records
A scraper or a form leaves a pile of professional profile URLs with no structured data attached. The agent calls Scrape Profiles to expand up to 50 URLs in one synchronous request, returning identity, role and company for each. Where the input is the other way around, a name plus a company or job title with no link, Find Profile URLs resolves up to 50 profile URLs in one call. For inbound signups arriving with only an address, Reverse Email Lookups handles between 2 and 50 addresses per request, which Icypeas prices at 10 credits per profile found, so the agent batches deliberately rather than calling it per record.
Human-in-Loop Highlight
A bulk file that reports completion is not the same as a bulk file that ran. Get Bulk Files separates aborted rows from rows that hit insufficient credits precisely because both happen, and both leave a hole in the output that nothing downstream will notice. Sequence the result and the missing rows do not bounce, do not error and do not appear anywhere. They simply never get contacted, and the accounts they belonged to look like accounts that were worked and did not respond. So the agent reads the counts and stops: "Bulk file [name] finished. [N] rows done, [N] emails found, [N] aborted, [N] hit insufficient credits. Certainty breakdown: [N] ultra_sure, [N] very_sure, [N] probable. [N] rows of the original [N] never ran. Sequence what completed, or top up and re-run the remainder first?" The campaign owner decides, because the right answer depends on whether the missing slice is random or happens to be the tier one accounts. That is human-in-the-loop doing the job it exists for. The agent surfaces the gap it would otherwise hide, and a person decides what an incomplete list is worth.
Agent Capabilities
17 actionsEmail Search
4- Submit Email Search Queues a search for one person's professional email from their name and company, returning a search ID immediately. Icypeas processes searches asynchronously, so poll Get Search Results with the returned ID until the status leaves NONE, SCHEDULED and IN_PROGRESS.
- Submit Email Verification Queues a deliverability check for a single address and returns a search ID to poll. Verification results carry a certainty of ultra_sure, very_sure, probable or undeliverable.
- Submit Domain Search Queues a search for the role-based addresses published on a company domain, such as contact@, admin@ and support@, returning a search ID to poll. Used when a generic company mailbox is the right route rather than a specific person.
- Get Search Results Reads the results of previously submitted searches, either a single search by its ID or every row of a bulk file. Each result carries a status and, when found, the emails with their certainty rating, MX provider and any phone numbers.
Bulk Processing
2- Submit Bulk Search Queues up to 5000 rows for email search, email verification or domain search in a single named file, returning a file ID. Populate only the row fields the chosen task needs.
- Get Bulk Files Lists bulk search files with their progress counts, including how many rows are done, how many emails were found, how many were aborted and how many hit insufficient credits, plus a breakdown of result certainties. Filterable to files still running.
Leads Database
4- Find People Searches the leads database for people matching a structured filter query and returns matching profiles synchronously. Filters cover name, current and past job titles and companies, school, skills, languages, seniority and location.
- Count People Returns how many people match a filter query without returning the profiles. Free to call, so use it to size an audience and tune filters before spending credits on Find People.
- Find Companies Searches the company database for organisations matching a structured filter query and returns them synchronously. Filters cover name, LinkedIn identifiers, domain, company type, industry, location, headcount, headcount growth and revenue.
- Count Companies Returns how many companies match a filter query without returning the records. Free to call, and the recommended way to validate an ideal customer profile before running Find Companies.
Profiles
4- Scrape Profile Retrieves the full public profile behind a single professional profile URL, returning identity, role and company details synchronously. Used to expand a bare profile link captured from a form or scraper into a structured record.
- Scrape Profiles Scrapes up to 50 professional profile URLs in one synchronous request, returning a structured record for each. Charged at 1.5 credits per profile returned.
- Find Profile URL Resolves a person's professional profile URL from their name plus either their company or their job title, at 1 credit per URL found. Used to attach a profile link to a contact that only has a name and employer.
- Find Profile URLs Resolves professional profile URLs for up to 50 people in one synchronous request, each entry needing a first and last name plus either a company or a job title. Used to backfill profile links across an imported list.
Reverse Lookup
2- Reverse Email Lookup Finds the person behind a single email address, returning identity, role and company synchronously. An expensive operation at 10 credits per profile found, so call it deliberately.
- Reverse Email Lookups Finds the people behind between 2 and 50 addresses in one synchronous request, materially faster than repeated single lookups. Charged at 10 credits per profile found.
Account
1- Get Subscription Information Returns the subscription plan and remaining credit information for the account, together with the account user ID. Used to check available credits before launching a bulk file, or to alert when the balance runs low.
Frequently Asked Questions
What can FlowRunner do with Icypeas?
FlowRunner agents can run Submit Email Search, Submit Email Verification, and Submit Domain Search in Icypeas, plus 14 more actions.
Does connecting Icypeas to FlowRunner require OAuth?
No. Icypeas connects to FlowRunner with an API key, no OAuth flow required.
Can Icypeas trigger a FlowRunner workflow automatically?
Icypeas doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Icypeas
$100 in credits. No card required. Connect in minutes.