Resources · Make integration

FindThatLead Make integrationAutomate FindThatLead with Make.

Every lead FindThatLead finds can move on its own to the next tool. The FindThatLead Make integration gives you 6 modules: 2 instant triggers and 4 actions. This guide is for sales and growth teams who want to connect the account, test a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the FindThatLead Make integration do for you?

The FindThatLead Make integration links your FindThatLead account to Make so the leads and email checks it produces feed a scenario, the automation you build in Make as a chain of modules. You pick what starts the flow, what FindThatLead does next and where the result goes, without writing code.

A clean list before any outreach. Watch a Lead starts the scenario when FindThatLead finds a new lead, and Verify an Email checks the address before it reaches your CRM or sequencing tool. Bad addresses stay out of your campaigns.

Prospects found from a company list. When a spreadsheet or a form hands Make a person and a domain, Search a Lead asks FindThatLead for the matching email. If you already have a LinkedIn profile, Search a Lead from Linkedin covers that case instead.

A log of every verification. Watch Email Verification fires each time an email is verified in FindThatLead, so the result can land in a shared sheet or a team channel for sales to review.

Know the limits: the Make documentation for FindThatLead is short and lists no field or quota. For anything the four actions miss, Make an API Call reaches the rest of the API with the same connection. The same app often has an n8n node too; see n8n vs Make before you choose, and the Make review or Make training if you are new to the tool.

Connect

How do you connect FindThatLead to Make?

  1. 01

    Add a FindThatLead module

    In your scenario, click the + and search for FindThatLead, then pick any module. Click Create a connection: a connection is your FindThatLead account linked to Make once and reused by every FindThatLead module.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps when several people or several FindThatLead accounts share the same Make organization. A name like the account owner or the team keeps the list readable later.

  3. 03

    Authorize and save

    Make then asks for access: either you approve it on the FindThatLead page, or you paste the key FindThatLead gives you. Click Save and the module is ready to use.

First scenario

Your first scenario with FindThatLead

GoalWhen FindThatLead finds a new lead, Make checks the email with Verify an Email.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor to add the first module.

  2. 02

    Add Watch a Lead

    Search for FindThatLead, pick Watch a Lead and create or choose your connection. This instant trigger waits for FindThatLead to call Make as soon as a lead is found.

  3. 03

    Add Verify an Email

    Click the + on the right of the trigger, pick Verify an Email and map the email address from the bundle the trigger received, a bundle being one item passed from one module to the next.

  4. 04

    Test with Run once

    Click Run once, then find a lead in FindThatLead. Open the bubble above each module to read the bundles it received and check the verification result.

  5. 05

    Switch it on

    When the test looks right, switch the scenario on. Each run then uses operations, one execution of one module on one bundle, which is what Make counts on your plan.

Triggers

What starts a FindThatLead scenario

2 modules start a scenario when something happens in FindThatLead. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by FindThatLead as soon as it happens.

FindThatLead1Watch a Lead

Watch a Lead

Instant trigger

In Make“Triggers when a new lead is found in FindThatLead”

Watch a Lead starts your scenario the moment FindThatLead finds a new lead, and hands that lead to the next module as a bundle.

How it fires
instant: the app calls Make through a webhook as soon as it happens, so there is no schedule to set on this module.
When to use it
pick it when every freshly found prospect should be checked, enriched or pushed to your CRM without anyone copying it by hand.
Watch out
the documentation lists no field for this trigger, so run the scenario once and read the bundle before you map anything.
FindThatLead2Watch Email Verification

Watch Email Verification

Instant trigger

In Make“Triggers when you verify an email in FindThatLead.”

You get a scenario run each time an email is verified in FindThatLead, with the verification passed along to the following module.

How it fires
instant: the app calls Make through a webhook as soon as it happens, so the scenario reacts to each check rather than on an interval.
When to use it
choose it when verifications happen inside FindThatLead itself and you want each outcome logged in a sheet or sent to the sales channel.
Watch out
the documentation does not say whether checks made by Verify an Email in Make fire it too; assume they might, keep the two in separate scenarios and test first.
Modules

What FindThatLead can do in a scenario

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

FindThatLead1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module lets you call any endpoint of the FindThatLead API from your scenario, using the connection you already created.

When to use it
reach for it when the three dedicated actions do not cover a request you need, since the Make documentation for this app is short.
Watch out
you write the request yourself, so keep the FindThatLead API reference open and test it with Run once before you rely on it.
FindThatLead2

Search a Lead

Action

In Make“Finds emails using FindThatLead algorithm.”

Search a Lead asks FindThatLead to find the email of a person, using its own finding algorithm, and returns the result to the scenario.

When to use it
use it when a new row in a prospect sheet or a form entry gives you a name and a company, and you want the email filled in.
Watch out
the Make documentation does not say which inputs it needs, so check the fields Make shows once the connection exists.
FindThatLead3

Search a Lead from Linkedin

Action

In Make“Finds leads from linkedin using FindThatLead algorithm.”

Starting from LinkedIn, this action looks up leads with the FindThatLead algorithm and brings the result back into your scenario.

When to use it
choose it over Search a Lead when the data you hold is a LinkedIn profile rather than a name and a company domain.
Watch out
the Make documentation gives no detail on what it accepts, so start with a single profile and Run once before scaling up.
FindThatLead4

Verify an Email

Action

In Make“Verifies an email using the FindThatLead algorithm.”

Verify an Email tells you whether an address looks usable, by running it through the FindThatLead verification algorithm inside your scenario.

When to use it
place it right after Watch a Lead or Search a Lead, before the contact reaches your CRM or email tool.
Watch out
each verification is one operation in Make; the documentation does not say whether it also fires Watch Email Verification, so test before pairing the two.
Need help

Need help automating FindThatLead with Make?

A person reads every message.

FAQ

FindThatLead and Make: common questions

01Is the FindThatLead Make integration free?
Yes, on the Make side. FindThatLead is a standard app, available from the Free plan. That plan allows 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) lower the interval to 1 minute and lift the active scenario limit. Make counts usage in operations, one per module run on one bundle. Your FindThatLead subscription is separate and not covered here.
02What do you need to connect FindThatLead to Make?
A FindThatLead account and a Make account. The Make documentation lists no prerequisite and no official connection steps for this app, so the generic flow applies: add a FindThatLead module, click Create a connection, give it a name if you like, approve access on the FindThatLead page or paste the key the app gives you, then click Save. The connection is then shared by every FindThatLead module in your scenarios, so you only do it once per account.
03Does the FindThatLead trigger in Make work in real time?
Yes. Both FindThatLead triggers are instant. Watch a Lead and Watch Email Verification are called by FindThatLead through a webhook as soon as the event happens, so they do not wait for the scenario schedule. This is different from scheduled triggers, which Make checks every 15 minutes by default on a new scenario. With an instant trigger, the scenario starts once per event, and each module it runs counts as an operation on your plan.
04What if a FindThatLead module is missing in Make?
Use Make an API Call. This module calls any endpoint of the FindThatLead API with the connection you already have, so it covers what the four listed actions and the two triggers do not. Make itself says its documentation for FindThatLead is limited for lack of public information, so field names and limits are not published there. Keep the FindThatLead API reference open while you build the request, and test with Run once before switching the scenario on.
05Should you use Make or n8n with FindThatLead?
It depends on the tool your team already runs. On Make, FindThatLead offers 6 modules: 2 instant triggers, 3 actions to find and verify emails, and Make an API Call for the rest. The same app often has an n8n node as well. Compare the modules each side offers for your use case, the way each tool is billed, and where the rest of your scenarios already live. Moving one integration alone rarely justifies switching platforms.