Resources · Make integration

GetEmail.io Make integrationAutomate GetEmail.io with Make.

Got a name and a company domain but no email address? The GetEmail.io Make integration gives you 3 modules: one instant trigger and 2 actions. This guide is for sales and growth teams, and it walks you from the connection to a first working scenario.

Try the GetEmail.io integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the GetEmail.io Make integration do?

The GetEmail.io Make integration links your GetEmail.io account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches an app or acts on it. Here, the bricks look up a person's email from a first name, a last name and a domain, and react when a search happens in GetEmail.io.

Enrich leads as they arrive. A signup form or a CRM hands over a name and a company website. Find an Email takes those three pieces and returns the address, which the next module writes back to the contact record.

Log every search your team runs. Sales reps often search inside GetEmail.io directly. Watch Instant Emails starts a scenario each time a search is made there, so you can copy the result to a shared sheet or post it in a team channel.

Reach the rest of the API. When the two ready-made modules are not enough, Make an API Call sends a request of your choice to GetEmail.io with the same connection.

One honest limit: Make states that its own documentation for GetEmail.io is limited, because little public information exists about the app. Test each module with Run once before trusting it in production. If you are still choosing a platform, read n8n vs Make, check Make pricing, or learn the editor with our Make training.

Connect

How do you connect GetEmail.io to Make?

  1. 01

    Add a GetEmail.io module

    In a scenario, click the + and search for GetEmail.io. Pick any of its modules, then click Create a connection. A connection is your GetEmail.io account linked to Make once and reused by every GetEmail.io module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when a team shares several accounts. Then follow the window: either approve access on the GetEmail.io page or paste the key GetEmail.io provides.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and the next GetEmail.io module you add will offer it in its list without asking again.

First scenario

Your first scenario with GetEmail.io

GoalWhen a new lead reaches another app with a name and a domain, Make finds the matching email address with GetEmail.io.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. This first module comes from the app that holds your leads, such as a CRM or a form tool.

  2. 02

    Set up the lead source

    Connect that app and choose where new leads appear. Each lead that flows out is a bundle: one item passed from a module to the next one.

  3. 03

    Add Find an Email

    Click the + on the right, search for GetEmail.io and pick Find an Email. Use your connection, then map the lead's first name, last name and domain from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can open each module to read the bundles it received and check the address GetEmail.io sent back.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule: every 15 minutes by default, one minute at the fastest on paid plans. Then switch the scenario on so it keeps working without you.

Triggers

What can start a GetEmail.io scenario?

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

GetEmail.io1Watch Instant Emails

Watch Instant Emails

Instant trigger

In Make“Triggers when an email is searched in different sources of GetEmail.io.”

Watch Instant Emails gives you a live feed of the email searches made in GetEmail.io, so each lookup can start a scenario on its own. It is the only trigger this app offers.

How it fires
it is an instant trigger, so GetEmail.io calls Make through a webhook as soon as a search happens, with no waiting for a schedule.
When to use it
your reps search by hand in GetEmail.io and you want every result copied to a shared sheet or a CRM without anyone pasting it.
Watch out
Make does not say whether a search run by Find an Email also fires this trigger. If it does, placing that module right after would loop, so test with Run once first.
Modules

What can GetEmail.io do in a scenario?

GetEmail.io gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

GetEmail.io1

Find an Email

Action

In Make“Retrieves an email address from given first name, last name and domain.”

Find an Email turns a first name, a last name and a company domain into an email address you can reuse in the rest of the scenario.

When to use it
a lead arrives from a form or a CRM with a name and a website but no address, and you want the contact completed before anyone follows up.
Watch out
each lookup counts as one operation, meaning one run of a module on one bundle, so filter out leads that already have an email.
GetEmail.io2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the GetEmail.io API from your scenario, reusing the connection you already created. It covers whatever the two listed modules leave out.

When to use it
you need a GetEmail.io feature that has no dedicated module in Make, and you know which request the API expects.
Watch out
you write the request yourself, so keep the GetEmail.io API reference open and test the call with Run once first.
Need help

Need help automating GetEmail.io with Make?

A person reads every message.

FAQ

GetEmail.io and Make: frequent questions

01Is the GetEmail.io Make integration free?
Yes, on the Make side. GetEmail.io is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two 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 one minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month. Your GetEmail.io subscription is a separate matter that this page does not cover.
02What do you need to connect GetEmail.io to Make?
A GetEmail.io account and a Make account. Make's documentation lists no specific prerequisite for this app. Add any GetEmail.io module, click Create a connection, name it if you want, then authorize Make on the GetEmail.io page or paste the key the app gives you, and click Save. The same connection then serves the trigger, Find an Email and Make an API Call. If the window asks for something unexpected, your GetEmail.io account settings are the first place to look.
03Does the GetEmail.io trigger in Make work in real time?
Yes. Watch Instant Emails is an instant trigger: GetEmail.io calls Make through a webhook as soon as a search happens, and the scenario starts right away. You do not pick an interval for it. The actions work differently, because they run only when something earlier in the scenario feeds them. If you start with Find an Email and a lead source from another app, the pace depends on that first module, which Make checks every 15 minutes by default, or as often as each minute on paid plans.
04What if a GetEmail.io module is missing in Make?
Use Make an API Call. It sends any request the GetEmail.io API accepts, with the connection you already set up, so you are not limited to the trigger and Find an Email. You need to know the endpoint and the parameters it expects, which Make does not document for this app. Make says itself that its GetEmail.io documentation is limited for lack of public information, so test every call with Run once and read the returned bundle before switching the scenario on.
05Should you use Make or n8n for GetEmail.io?
It depends on the tool your team already runs. On Make, GetEmail.io brings 3 modules: one instant trigger, Find an Email and Make an API Call, which together cover lead enrichment and the rest of the API. The same app often has an n8n node as well, so check what n8n offers for it before deciding. Neither tool is ranked here. Pick the one where your other apps and your team's habits already live, and compare the two platforms on the n8n vs Make page linked above.
Same platform

Other docs you might need on this stack.

Browse all integrations