Resources · Make integration

Lusha Make integrationAutomate Lusha with Make.

Every new lead can arrive with verified contact and company details already attached. The Lusha Make integration gives you 11 modules: 7 actions and 4 searches. This page shows sales and ops teams how to link the account, build a first scenario and pick the right module.

Try the Lusha integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Lusha Make integration do for your pipeline?

The Lusha Make integration lets a Make scenario, the automation you build as a chain of modules, ask Lusha for contact and company data whenever another tool hands it a lead. You link your Lusha account once with an API key, and every Lusha module reuses that link.

Enrich an inbound lead. A form or CRM passes a name and a company to Find a Contact, and Find a Company adds the firm behind it, so a rep opens a complete record instead of a bare email.

Build a target list. Prospecting Search queries contacts or companies with Lusha filters, then Prospecting Enrich pulls the full details of what the search returned. Get Company Recommendations widens the list with firms similar to your best accounts.

Watch accounts that move. Get Company Signals and Get Contact Signals retrieve events such as job changes or funding for the people and firms you already track, so outreach starts from a reason to call.

One limit to know upfront: Lusha has no trigger in Make. It never starts a scenario on its own, so the first module comes from another app or from the Make schedule. Anything the listed modules skip goes through Make an API Call. If you are weighing tools, the n8n vs Make comparison helps, and the Make pricing page explains how operations are counted. Teams that want a hand can look at the Make training.

Connect

How do you connect Lusha to Make?

  1. 01

    Generate your Lusha API key

    Log in to Lusha, click API in the header bar, then Generate Key on the Lusha API page. Copy the key and keep it somewhere safe: Make will ask for it in a moment, and an active Lusha account is required.

  2. 02

    Open the connection window

    In your Make scenario, add any Lusha module and click Create a connection. A connection is your Lusha account linked to Make once and reused by every Lusha module. You can type a label in Connection name, which is optional.

  3. 03

    Paste the key and save

    Paste the key into the API Key field and click Save. From then on, every Lusha module in any of your scenarios can pick this connection from the list instead of asking again.

First scenario

Your first scenario with Lusha

GoalWhen a new lead reaches another app, Make asks Lusha for the person's details and then for the company behind them.

  1. 01

    Start from the lead source

    On the Scenarios page, create a new scenario and click the +. Since Lusha has no trigger, pick the app where leads land first, such as your form tool or CRM, and connect it.

  2. 02

    Add Find a Contact

    Click the + on the right of that first module, search for Lusha and choose Find a Contact. Select the connection you created, or click Create a connection if this is your first Lusha module.

  3. 03

    Map the lead into Lusha

    Fill the module fields by mapping the lead details the first module received. Each lead is one bundle, an item that flows from one module to the next, and Lusha looks it up.

  4. 04

    Add Find a Company

    Click the next + and add Find a Company. It looks a firm up by domain or by name, so map the company from the lead or from what Find a Contact returned.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and check that Lusha sent back the person and the company.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on each bundle is one operation, the unit Make counts on your plan.

Modules

What each Lusha module does in Make

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

Lusha1

Find a Company

Action

In Make“Gets a company by its domain or by its name.”

Hand Lusha a domain or a company name and get the matching company record back, ready to map into your CRM or sheet.

When to use it
a lead gives you only a work email or a firm name and your team wants the account context before the first call.
Watch out
a name can be ambiguous, so pass the domain whenever the lead provides one.
Lusha2

Find a Contact

Action

In Make“Gets a contact by its specified parameters.”

Turn the few details a lead leaves behind into one Lusha contact, with the data Lusha holds on that person, for a single lead at a time.

When to use it
right after a demo request or a trade show scan, when one person needs a complete profile before a rep reaches out.
Watch out
for a list of people whose Lusha IDs you already hold, Bulk Find Contacts fits better than repeating this module.
Lusha3

Get Company Recommendations

Action

In Make“Get company recommendations based on other companies”

Feed Lusha companies you already know and receive other firms that resemble them, a quick way to grow an account list from your best customers.

When to use it
a deal closes and marketing wants lookalike accounts to target next with the same pitch.
Watch out
the output is a suggestion list, so route it to a review sheet before it reaches your CRM.
Lusha4

Get Company Signals

Action

In Make“Retrieve signals for companies. Each company can be identified by: (1) Company ID, (2) Company domain, or (3) Company name”

Retrieve the signals Lusha records on a company, such as funding news, identifying each firm by its Lusha ID, its domain or its name.

When to use it
an account manager wants a heads-up on target accounts before planning outreach, fed from the list the team already keeps.
Watch out
the Lusha ID is the most precise identifier, so store it when an earlier module returns it.
Lusha5

Get Contact Recommendations

Action

In Make“Fetch recommended contacts by supplying contact IDs to return similar profiles”

Supply the Lusha IDs of contacts who fit your target and get back similar profiles, a way to find more buyers like the ones who already said yes.

When to use it
a champion signs, and sales wants peers with a comparable profile at other accounts.
Watch out
this module needs contact IDs, not emails, so run a find or search module first to get them.
Lusha6

Get Contact Signals

Action

In Make“Retrieve signals for contacts. Each contact can be identified by: (1) Contact ID, (2) LinkedIn URL, (3) Email address, or (4) Full name + Company (name or domain)”

See what changed for a person, such as a new job, by pointing Lusha at a contact ID, a LinkedIn URL, an email address, or a full name with the company.

When to use it
a former customer contact may have moved to a new firm, which is often a warm opening for sales.
Watch out
a full name alone is not enough; pair it with the company name or domain.
Lusha7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the Lusha API from your scenario, with the same connection, when none of the ten ready-made modules covers the request you have in mind.

When to use it
a Lusha feature your team relies on has no dedicated module in Make yet.
Watch out
you build the request yourself, so keep the Lusha API documentation open while you fill it.
Lusha8

Bulk Find Companies

Search

In Make“Gets companies by their ID and specified parameters.”

Look up several companies in one request by their IDs and chosen parameters, and receive each result as its own bundle for the next module.

When to use it
you stored Lusha company IDs in a sheet or CRM, and those accounts need refreshing in one pass rather than one at a time.
Watch out
each returned company flows as a separate bundle, and every module after it runs once per company.
Lusha9

Bulk Find Contacts

Search

In Make“Gets contacts by their ID and specified parameters.”

Pull many contacts at once by their IDs and parameters, so an entire list gets its Lusha data in a single module instead of a loop of lookups.

When to use it
contacts you already found in Lusha, with their IDs saved, need fresh data before they land in your sequencing tool.
Watch out
a search can return zero results, so add a filter before any module that expects data.
Lusha10

Prospecting Enrich

Search

In Make“Get full details of Contacts and Companies from the search results”

Take what Prospecting Search found and fetch the full details of those contacts and companies, which turns a raw result list into records worth saving.

When to use it
place it directly after Prospecting Search, once the filters return the right people.
Watch out
it works on search results, so it has nothing to enrich unless the search module runs before it.
Lusha11

Prospecting Search

Search

In Make“Query Contacts or Companies using the available filters”

Query Lusha for contacts or companies with its available filters and build a fresh prospect list without opening the Lusha interface.

When to use it
a new market or persona needs a starting list, and you want it to land straight in a sheet.
Watch out
the search returns the matches only; add Prospecting Enrich after it when you need their full details.
Need help

Need help automating Lusha with Make?

A person reads every message.

FAQ

Lusha and Make: common questions

01Is the Lusha Make integration free?
Yes on the Make side. Lusha is a standard app, available from the Make Free plan, which allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits per month. On the Lusha side, you still need an active Lusha account with an API key, and its subscription is set by Lusha, not by Make.
02What do you need to connect Lusha to Make?
An active Lusha account and a Lusha API key. In Lusha, click API in the header bar, then Generate Key, and copy the value. In Make, add a Lusha module, click Create a connection, optionally name it, paste the key into the API Key field and click Save. The connection is then reused by every Lusha module you add later, in this scenario or in any other one, so the key is pasted only once.
03Can Lusha start a Make scenario on its own?
No. Lusha has no trigger module in Make, so it cannot launch a scenario when something happens in Lusha. The scenario starts elsewhere: a trigger from another app, such as a form or a CRM that receives new leads, or the Make schedule set on the first module, every 15 minutes by default. The Free plan keeps at least 15 minutes between scheduled runs, and paid plans go down to 1 minute.
04What if a Lusha module is missing in Make?
Use Make an API Call. Lusha has this module in Make, and it can reach any endpoint of the Lusha API with the connection you already set up, so a feature without a dedicated module is still within reach. You write the request yourself, which asks for a look at the Lusha API documentation. The Make documentation for Lusha lists no numeric limit for these modules, so there is no published cap to plan around there.
05Should you use Make or n8n for Lusha?
It depends on the tool your team already runs. Make offers 11 Lusha modules, with finds, signals, recommendations, bulk lookups, prospecting search and enrich, plus Make an API Call for the rest, all behind a visual editor and a guided connection. n8n often has a node for the same apps, so check its Lusha coverage against the modules you need. Pick the platform where the lookups your scenario depends on already exist.
Same platform

Other docs you might need on this stack.

Browse all integrations