Resources · Zapier integration

Icypeas Zapier integrationAutomate Icypeas with Zapier.

The Icypeas Zapier integration gives you 10 actions and no trigger. You find emails, verify them, locate company and profile URLs and scrape them, but the Zap always starts in another tool. Here is how to wire it, and what it costs.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Icypeas Zapier integration actually does

Zapier lets Icypeas, an email finder that works from open sources, run inside your other tools through a Zap: an automation that starts on an event in one app (the trigger) and then does things for you (the actions). Icypeas only brings actions, so it always plays the second part: something happens elsewhere, then Icypeas looks it up.

An email next to every new lead. A sales rep adds a name and a company to the CRM; Email Search or Email Search Sync takes the first name, last name and company or domain and looks for the matching address. No more copying names into a search box one by one.

A list that does not bounce. Before a sequence goes out, Email Verification or Email Verification Sync checks an address you already have. Agencies that inherit contact lists from clients run each address through it before a campaign.

Account research on autopilot. Company URL Finder turns a company name into its URL, Profile URL Finder does the same for a person, and the two scrapers then read those pages. A prospect record gets richer without anyone opening a browser tab.

What Zapier does not do here: it cannot start a Zap from Icypeas, since the app exposes no trigger, and it offers no search step to look up something already stored in your Icypeas account. Fetching the result of an earlier search goes through an action, Get Single Results, which needs IDs you have to carry yourself.

Comparing platforms for the same job? The Icypeas Make integration page is the companion of this one, and n8n vs Zapier is there if you are still choosing between the two.

Vocabulary

Zapier vocabulary in one minute

Seven words you will meet on every line below, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event that starts a Zap, like a new contact in your CRM. Icypeas has none, so the trigger always comes from another app.
Action
What the Zap does once started: the step that writes, sends or looks something up for you. Every Icypeas operation is one.
Task
The unit Zapier bills: one action that completes successfully. The allowance on your plan is simply a count of those.
Polling vs instant
A polling trigger is checked on a timer set by your plan. An instant trigger is pushed by the app the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something already stored in an app, so later steps can reuse it. Icypeas offers none on Zapier.
Cost

What an Icypeas Zap really costs

With Icypeas, every useful step is an action, so every useful step is billed.

  • Trigger (other app)Free, never counted
  • Each successful Icypeas action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • Icypeas on the free planYes, not a premium app

The trigger in your other app costs nothing, and neither does checking it for new data. Each Icypeas action that succeeds counts as one task, and in a Zap with several actions each one counts separately: find then verify an email and you use two tasks per lead. An action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, limited to two steps: one trigger, one action. Chaining two Icypeas actions, or adding a filter, makes the Zap multi-step and requires a paid plan. Icypeas is not a premium app, so it runs on the free plan.

Connect

Connect Icypeas to Zapier

  1. 01

    Open the Apps page

    In Zapier, go to Apps and click + Add connection. A connection is your Icypeas account linked once, then reused by every Zap step that calls Icypeas.

  2. 02

    Pick Icypeas

    Search for Icypeas in the dialog, select it, then click Add connection. You need an Icypeas account of your own before going any further with the connection.

  3. 03

    Sign in and grant access

    A new tab opens on Icypeas. Sign in and let Zapier work with the account. Zapier then works with what this account can reach, so connect the account your searches run under.

First Zap

Your first Zap: find and verify a lead's email

GoalWhen a contact lands in your CRM without an email, look for the address with Icypeas, then run it through a verification before anyone writes to it.

  1. 01

    Build: set the trigger

    Create a Zap and pick your CRM as the starting app, with its event for a new contact. Icypeas has no trigger, so the Zap always starts in the tool where leads arrive.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent contacts from that account, so you map the next steps on a real lead with a real name and company.

  3. 03

    Add the email search

    Add Icypeas with Email Search Sync. Map the first name, last name and company name or domain from the CRM contact. All three are required. Test the step and check that the address shows up in what came back.

  4. 04

    Add the verification

    Add Email Verification Sync and map the address returned by the previous step into its Email field. With two actions, this is a multi-step Zap and needs a paid plan.

  5. 05

    Test, then Publish

    Test each step and read what came back before going further. Then click Publish. Each new contact now uses two tasks, one per Icypeas action.

Actions

Icypeas actions on Zapier

Icypeas gives you 10 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Company Scraper

Action

In Zapier“Requires the URL of the company you want to scrap”

Reads the company page whose URL you give it and brings its information back into the Zap for the next steps.

When to use it
after Company URL Finder, to enrich an account record in your CRM before a sales call.
Watch out
the company URL is required; pair it with Company URL Finder when your source only holds names.
2

Company URL Finder

Action

In Zapier“Requires the company name or domain to find it's URL.”

Turns a company name or domain into the company's URL, the address you then hand to the company scraper.

When to use it
your form only asks for a company name, and you want the matching company page on file.
Watch out
the company name or domain is required; a form field that visitors can skip leaves the step with nothing to look for.
4

Email Search Sync

Action

In Zapier“Requires the first name, last name, and company name or domain.”

The second version of the email search, with the same three required inputs: first name, last name, and company name or domain.

When to use it
when your test shows the address coming back in this step, so the very next step can verify it or write it back.
Watch out
run a test on both versions in the editor and compare what each returns before you settle on one for a live Zap.
6

Email Verification

Action

In Zapier“Requires the email you want to verifiy”

Checks an email address you already have, before a sequence writes to it.

When to use it
a list bought or inherited from a client goes through verification before it enters any sequence.
Watch out
it takes one address per run, so a long list means one run, and one task, per address.
7

Email Verification Sync

Action

In Zapier“Requires the email you want to verifiy”

The other version of the verification, with the same single required field: the email to check.

When to use it
right after an email search in the same Zap, so the address found is checked before it goes anywhere.
Watch out
as with the two email searches, test both versions side by side and keep the one whose output fits your next step.
8

Get Single Results

Action

In Zapier“Get results for your single searches”

Retrieves the results of a single search you already sent, using its Search ID, your User id and the search mode, single or bulk.

When to use it
a search was sent in one Zap and its outcome has to be collected in a later step or another Zap.
Watch out
all three fields are required, and the Search ID only exists once a single search has been sent.
9

Profile Scraper

Action

In Zapier“Requires the URL of the profile you want to scrap”

Reads the profile page at the URL you provide and returns what it gathered to the following steps.

When to use it
a consultant preparing a meeting wants the attendee's profile details on the contact record automatically.
Watch out
no URL, no scrape; chain it after Profile URL Finder if your trigger only carries a name.
10

Profile URL Finder

Action

In Zapier“Requires the first name, the last name and the company or the title job to find it's URL.”

Finds the URL of a person's profile from their first name and last name, helped by their company or job title.

When to use it
a recruiter receives a candidate's name and current employer, and wants the profile link next to the application.
Watch out
only first and last name are marked required, yet the action's own description also asks for the company or the job title, so map one of them too.
When it breaks

When an Icypeas Zap breaks

Zapier attaches no help article to Icypeas, so the failures below are the general ones of Zapier, as they play out with this app.

None of these is specific to Icypeas, but each one takes its own shape when a Zap enriches leads. If you would rather have someone diagnose it, see our Zapier troubleshooting page.

  • Your existing leads are never processed

    A Zap only reacts to what happens after it is switched on. The contacts already in your CRM are not replayed; enriching them is a separate job.

  • The Zap feeds itself

    If the trigger watches contacts and the Zap writes Icypeas results back into those same contacts, it can start itself again and again and burn through tasks.

  • A bulk import holds the Zap back

    When your trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold the runs instead of firing them all.

  • A polling trigger skips items it has seen

    On a polling trigger, Zapier remembers what it already picked up, so the same contact does not start the Zap a second time. One contact, one lookup.

  • Get Single Results has nothing to fetch

    Without a Search ID from an earlier single search, plus your User id and the search mode, this step cannot run. Carry the ID from the step that sent the search.

  • A failed action is not billed

    An action that fails is not billed, which spares your tasks. It also means that lead was not enriched on that run, so test every step before you publish.
Need help

Need help automating Icypeas with Zapier?

A person reads every message.

FAQ

Icypeas Zapier integration: common questions

01Is the Icypeas Zapier integration free?
On the Zapier side, yes. Icypeas is not a premium app, so it works on the free Zapier plan, which includes 100 tasks a month and unlimited Zaps. The limit is the shape of the Zap: on the free plan, a Zap has two steps, one trigger in another app and one Icypeas action. Finding then verifying an email in the same Zap takes two actions, which makes it multi-step and requires a paid plan. Start with a single action, check that it does what you expect, and add the second step once you move to a paid plan.
02How many tasks does an Icypeas Zap use?
One task per Icypeas action that succeeds, every time the Zap runs. The trigger in your other app costs nothing, and checking it for new data costs nothing either. A Zap that searches for an email and then verifies it uses two tasks per lead. An action that fails is not counted. A few apps and actions take more than one task when they complete, so keep that in mind for the other apps in your Zap.
03Does Icypeas run in real time on Zapier?
It depends on the app that starts the Zap, because Icypeas has no trigger of its own. If that app offers an instant trigger, it tells Zapier the moment a new contact appears and the Icypeas action runs straight away, on any plan. If it uses a polling trigger, Zapier checks it at an interval set by your plan: every 15 minutes on Free, 2 on Professional, and 1 on Team and Enterprise. Pick the starting app with that in mind.
04What does it take to connect Icypeas to Zapier?
An Icypeas account and a Zapier account. In Zapier, open Apps, click + Add connection, search for Icypeas, click Add connection, then sign in to Icypeas in the tab that opens and grant access. If you plan to use Get Single Results, also note your Icypeas User id, which you find in the API section of your profile. The connection is made once and reused by every Zap that calls Icypeas.
05Why are there two versions of Email Search and Email Verification?
Zapier lists Email Search next to Email Search Sync, and Email Verification next to Email Verification Sync, each pair with the same required inputs. The official descriptions do not spell out the difference for a Zap, so the safe move is practical: build the step with one version, run the test, read what comes back, then do the same with the other. Keep the version whose output your next step can actually use, and stick to it across your Zaps.
06What if the Icypeas action you want is not in Zapier?
Then it is not available through this integration today. Zapier offers ten Icypeas actions, covering email search and verification, company and profile URLs, scraping and the retrieval of single search results, but no trigger and no search step. If your idea depends on Icypeas starting the Zap, it cannot work as is: the Zap has to start in another app, such as your CRM or your form tool, and call Icypeas afterwards. Check the list above before planning the rest.
07Zapier, Make or n8n for Icypeas?
It depends on your criteria rather than on a winner. On Zapier the facts are known: ten actions, no trigger, the integration works on the free plan, and every successful action counts as one task. For Make and n8n, check the same three things on their side: which Icypeas operations they expose, how they bill each run, and whether any of them can start a scenario from Icypeas. Then keep the platform whose operations cover your use case.
Same platform

Other docs you might need on this stack.

Browse all integrations