Resources · Make integration

Icypeas Make integrationAutomate Icypeas with Make.

Can Make find and check emails with Icypeas for you? Yes. The Icypeas Make integration gives you 13 modules, 12 actions and 1 instant trigger, to look up emails, domains and profiles from any list of leads. This page shows how to plug in your API key and build a first scenario without code.

Try the Icypeas integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Icypeas Make integration do for your prospecting?

The Icypeas Make integration links your Icypeas account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick of that chain. With Icypeas, those bricks find a professional email from a name and a company, verify an address, or work from a company or profile URL.

A clean list before a campaign. A sales team collects leads with a first name, a last name and a company. Single Email Search looks for the professional address, then Single Email Verification checks it before your outreach tool sends anything.

Company records built from a name. Give Company URL Search a domain or a company name to get the company URL, then hand that link to Company Scraper so the account gets details instead of a bare name.

Profiles matched to real people. Recruiters can send a name plus an employer or a job title to Profile URL Search, then pass the profile URL it finds to Profile Scraper.

Know the limits before you start. Several modules carry a Deprecated label in Make, including the only trigger, so pick the versions marked with a check. Make's documentation for this app is AI-generated from the Icypeas docs and may contain mistakes. When a feature has no module, Make an API call reaches the rest of the Icypeas API with the same connection.

New to the editor? The Make training covers the basics, Make pricing explains how operations are counted, and n8n vs Make helps if you are also looking at n8n, where the same app often has a node.

Connect

How do you connect Icypeas to Make?

  1. 01

    Start a connection

    Open your scenario, add any Icypeas module and click Create a connection. A connection is your Icypeas account linked to Make once, then reused by every Icypeas module you add afterwards.

  2. 02

    Copy the API key in Icypeas

    In Icypeas, open the API section in the sidebar, switch API access on with its toggle, and copy the API key shown on screen. This needs an active Icypeas account.

  3. 03

    Paste it into Make

    Back in Make, type a name in Connection name if you want one (it is optional), paste the credentials you copied from Icypeas and save. All Icypeas modules can now use this connection.

First scenario

Your first Icypeas scenario: find an email, then verify it

GoalWhen a new lead appears in another app, Make finds the lead's email with Icypeas and checks it before use.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Start with the app that holds your leads, a sheet or a CRM, because the only Icypeas trigger is deprecated.

  2. 02

    Add Single Email Search

    Click the + to the right of that first module, search for Icypeas and pick Single Email Search, the one with the check mark. Choose your connection or create it now.

  3. 03

    Map the lead's details

    Map the first name, the last name and the domain or company name from the previous module. Each lead travels as a bundle, which means one item passed from one module to the next.

  4. 04

    Add the verification

    Click the next +, add Single Email Verification and map the email found by the search. That way you see the check result for each address before the rest of your flow uses it.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and you can open each module to read the bundles it received. One module run on one bundle is one operation on your plan.

  6. 06

    Schedule and switch on

    Open the clock on the first module to set Scheduling; a new scenario runs every 15 minutes by default. Switch the scenario on and it keeps working without you.

Triggers

What can start an Icypeas scenario?

1 module starts a scenario when something happens in Icypeas. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Icypeas as soon as it happens.

Icypeas1⛔ [Deprecated] Watch Single Result

⛔ [Deprecated] Watch Single Result

Instant trigger

In Make“Watch result from your single search using a webhook. You need to copy/paste the webhook URL in [here](https://app.icypeas.com/bo/profile) (section API)”

Watch Single Result hands your scenario the outcome of a single search launched in Icypeas, as soon as that outcome is ready. It relies on a webhook URL that you copy from Make and paste into the API section of your Icypeas profile.

How it fires
instant. Icypeas calls Make through a webhook as soon as it happens, so there is no polling interval to pick.
When to use it
only to keep an older scenario alive while you rebuild it.
Watch out
Make labels this trigger deprecated. For new work, start from another app and call the Icypeas modules marked with a check.
Modules

What can Icypeas do inside a Make scenario?

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

Icypeas1

✅ Company Scraper

Action

In Make“Requires the company URL.”

Company Scraper takes a company URL and brings back what Icypeas pulls from it, ready to map into your CRM or sheet. It turns a bare link into a company record you can actually use.

When to use it
you already hold the company URL, for example right after Company URL Search found it.
Watch out
the company URL is its required input, so make sure an earlier module really filled it.
Icypeas2

✅ Company URL Search

Action

In Make“Requires the domain or company name.”

Company URL Search works the other way round: you give it a domain or a company name, and it looks for the matching company URL. Handy when a list holds names and nothing else.

When to use it
before Company Scraper, when an inbound form or an event list gives company names without links.
Watch out
a domain is more specific than a name, so send the domain whenever you have it.
Icypeas3

Deprecated

Action

In Make“Requires the person's first name and last name, and a domain or company name.”

This older email search still shows up in Make under the plain name Deprecated. It asks for a first name, a last name and a domain or company name, just like the current search.

When to use it
only if an existing scenario already relies on it and you are not ready to swap it out.
Watch out
for any new build, pick Single Email Search with the check mark, which takes the same inputs.
Icypeas4

⛔ [Deprecated] Get Single Result

Action

In Make“Get result from your single search. You need the **_id** that was returned when launching your single search.”

Get Single Result collects the outcome of a single search you launched earlier, using the _id Icypeas returned at launch. It belongs to the older two-step way of working: launch first, fetch later.

When to use it
in legacy scenarios that store that _id and come back for the answer.
Watch out
Make marks it deprecated, and without the exact _id there is nothing to retrieve.
Icypeas5

⛔ [Deprecated] Single Email Search

Action

In Make“Requires the person's first name and last name, and a domain or company name.”

The deprecated Single Email Search is the previous version of the email finder. Feed it a first and last name plus a domain or company name, and it searches for that person's professional address.

When to use it
keep it only in scenarios built before the current version.
Watch out
two modules share this name in the list; the one with the check mark is current, so read the label before you click.
Icypeas6

⛔ [Deprecated] Single Email Verification

Action

In Make“Requires the email you want to verify.”

An older way to test one email address before you use it. You pass the address you want to verify, and Icypeas returns its verdict to the scenario.

When to use it
only while an existing scenario still points to it.
Watch out
a newer Single Email Verification with a check mark sits right next to it in Make; move your mappings over the next time you edit the scenario.
Icypeas7

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API call lets your scenario reach any endpoint of the Icypeas API through the connection you already set up. No second key to paste, no extra login.

When to use it
when none of the listed modules covers what you need from Icypeas.
Watch out
you have to know which endpoint you are calling, so keep the Icypeas API documentation open while you fill it in.
Icypeas8

✅ Profile Scraper

Action

In Make“Requires a personal profile URL.”

Give Profile Scraper a personal profile URL and it returns what Icypeas extracts about that person, so a lone link becomes a filled-in contact in your scenario.

When to use it
after Profile URL Search, or whenever a form or a sheet already stores profile links.
Watch out
it expects a personal profile URL, not a company page; company links belong in Company Scraper.
Icypeas9

✅ Profile URL Search

Action

In Make“Requires the person's first name, last name, and either a company name or a job title.”

Starting from a name, Profile URL Search looks for the matching personal profile URL. It needs a first name, a last name, and either a company name or a job title to narrow things down.

When to use it
a recruiter has a shortlist of names with their current employer and wants the profile links before reaching out.
Watch out
map a company name or a job title every time, because the name alone is not enough here.
Icypeas10

✅ Single Domain Search

Action

In Make“Requires the domain or company name you want to search.”

Single Domain Search runs a lookup on one domain or company name, which is what you want when the organization matters more than one specific person.

When to use it
a new account lands in your pipeline and you want Icypeas results on its domain before choosing who to contact.
Watch out
it handles one domain per run, so a list of companies costs one operation per bundle.
Icypeas11

✅ Single Email Search

Action

In Make“Requires the person's first name and last name, and a domain or company name.”

This is the current email finder, and the Icypeas module most scenarios start with. Send a first name, a last name and a domain or company name; Icypeas answers with the professional address it finds.

When to use it
every time a lead reaches you without an email, from a webinar list, a form or a CRM.
Watch out
finding an address and checking it are two separate modules, so pair it with Single Email Verification.
Icypeas12

✅ Single Email Verification

Action

In Make“Requires the email you want to verify.”

You get Icypeas's verdict on one email address, so you can decide what reaches your outreach tool based on a real check. Pass the address, Icypeas does the rest.

When to use it
right after Single Email Search, or on an old list you plan to contact again.
Watch out
each address is one bundle and one operation, so remove duplicates earlier in the scenario.
Need help

Need help automating Icypeas with Make?

A person reads every message.

FAQ

Icypeas and Make: common questions

01Is the Icypeas Make integration free?
Yes, on the Make side. Icypeas is a standard app, available from the Free plan, which gives you 2 active scenarios, a 15-minute minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Each module run counts as an operation against your monthly credits. You still need an active Icypeas account with an API key, and that subscription is handled by Icypeas, not by Make.
02What do you need to connect Icypeas to Make?
You need two things: an active Icypeas account and its API key. In Icypeas, open the API section of the sidebar, turn API access on and copy the key displayed. In Make, add any Icypeas module, click Create a connection, name it if you want, and paste the key. That single connection then serves all 13 Icypeas modules. If the first module you add is the instant trigger, Make asks you to create a webhook first and the connection second.
03Does the Icypeas trigger in Make work in real time?
Yes, but it is deprecated. Watch Single Result is an instant trigger: Icypeas calls Make through a webhook as soon as a single search result is ready, once you paste the webhook URL into the API section of your Icypeas profile. Because Make labels it deprecated, a safer start for a new scenario is another app, such as a form or a spreadsheet, followed by Single Email Search. The first module then sets the pace, on a schedule of every 15 minutes by default, or through a webhook if that app offers one.
04What if an Icypeas module is missing in Make?
Use Make an API call. It reaches any endpoint of the Icypeas API with the connection you already created, so you can cover features the 12 action modules do not list. Before building on it, keep in mind that Make's page for this app is AI-generated from the Icypeas documentation and may contain mistakes, so confirm important details with Icypeas directly. Also read the labels: several modules are marked deprecated, and for email search and verification a current version with a check mark sits right next to them.
05Should you use Make or n8n for Icypeas?
It depends on your team. Make gives you 13 Icypeas modules in a visual editor, where each scenario is tested with Run once and then switched on with a schedule, which suits people who like to see every step. The same app often has an n8n node too, so check what that node covers before deciding. Compare the modules you actually need, the way your team prefers to build, and how each tool counts usage. Neither choice is right for everyone, and the comparison page linked earlier on this page goes deeper.
Same platform

Other docs you might need on this stack.

Browse all integrations