Resources · Make integration

Leadinfo Make integrationAutomate Leadinfo with Make.

What happens to a company Leadinfo spots once it reaches Make? The Leadinfo Make integration gives you 1 instant trigger that hands each company to a scenario. This guide is for sales and marketing teams who want those companies in their other tools, and it walks you through a first working build.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Leadinfo Make integration let you automate?

The Leadinfo Make integration passes the B2B companies Leadinfo spots on your website into Make, the tool where you build a scenario (an automation made of connected steps). It has one module, the Watch Company trigger, and every other step comes from the apps you already use.

A CRM that fills itself. Watch Company receives a company as soon as Leadinfo sends it. Add your CRM's module after it and each company becomes a record, with no copy and paste from the Leadinfo screen.

A sales alert with context. Instead of a CRM, point the company to a team chat or an email module. The right salesperson reads the name of the business that just showed buying interest while it is still fresh.

Outreach that starts on its own. Route the company to your email or sequencing tool so a personalized follow-up can begin without anyone opening a spreadsheet.

Know the limits before you plan. Leadinfo has no action, no search and no Make an API Call module in Make, so the scenario can only react to what Leadinfo sends, never ask Leadinfo for more. Make also says its documentation for this app is limited, which is why your first test run matters. If you are weighing the two platforms, the n8n vs Make comparison sets out the criteria, the Make training covers scenario building from scratch, and Make troubleshooting helps when a run fails.

Connect

How do you connect your Leadinfo account to Make?

  1. 01

    Add the Leadinfo module

    In a new scenario, click the +, search for Leadinfo and pick Watch Company. Then click Create a connection. A connection is your Leadinfo account linked to Make once and reused afterwards.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps. Something like the workspace or the team it serves makes it easy to pick the right account later, especially if several people share one Make organization.

  3. 03

    Authorize and save

    The docs do not say which method Leadinfo uses, so depending on what Make shows, you either approve access on a Leadinfo page or paste a key that Leadinfo gives you. Follow the window, then click Save. The module is ready to receive companies.

First scenario

Your first scenario with Leadinfo

GoalWhen Leadinfo sends a company, Make passes it to the next app of your choice, such as your CRM.

  1. 01

    Create the scenario

    Open the Scenarios page and create a new scenario. Click the large + in the middle of the editor to add the first module, the one that starts everything.

  2. 02

    Add Watch Company

    Search for Leadinfo, choose Watch Company and select the connection you just made. The lightning badge on the module tells you it is instant: Leadinfo calls Make, Make does not poll.

  3. 03

    Add the destination

    Click the + on the right of Watch Company and add the module of the app that should get the company, for example your CRM. Map the company details from Leadinfo into its fields.

  4. 04

    Test with Run once

    Click Run once, then send a company from Leadinfo. Each module shows the bundles it received, a bundle being one item passed along, here one company. Check that the details land where you expect.

  5. 05

    Switch the scenario on

    Once the test looks right, save and switch the scenario on. From then on, every company Leadinfo sends runs through it, and each module execution counts as one operation on your Make plan.

Triggers

The Leadinfo trigger

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

Leadinfo1Watch Company

Watch Company

Instant trigger

In MakeTriggers when a company is send from Leadinfo to make.

Watch Company gives your scenario a starting point: each company Leadinfo sends to Make arrives as a bundle that the next modules can file, share or act on. It is the only Leadinfo module in Make, so every build with this app begins here.

How it fires
instant, meaning Leadinfo calls Make through a webhook as soon as it sends the company.
When to use it
whenever a visiting company should reach your CRM, a sales channel or an outreach tool without manual export.
Watch out
the documentation is limited, so test with Run once before trusting your field mapping.
Need help

Need help automating Leadinfo with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Leadinfo Make integration free?
Yes, on the Make side. Leadinfo is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a run time of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Its 15 minute minimum interval applies to scheduled scenarios, and Watch Company is instant. Paid plans (Core, Pro, Teams and Enterprise) lift the active scenario cap and allow runs of up to 40 minutes. Your Leadinfo subscription is a separate matter.
02What is needed to connect Leadinfo to Make?
A Leadinfo account and a Make account. Make's documentation lists no specific prerequisite for this app and gives no dedicated connection steps, so the generic Make flow applies. Add Watch Company, click Create a connection, give it a name if you like, then either approve access on the Leadinfo page or paste the key Leadinfo provides, and click Save. The connection is stored once and reused by any Leadinfo module in your other scenarios, which keeps credentials in a single place.
03Does the Leadinfo trigger react in real time?
Yes. Watch Company is an instant trigger, marked with a lightning badge in the editor. Leadinfo calls Make through a webhook as soon as it sends a company, so the scenario runs right away instead of waiting for a polling interval. The default schedule of every 15 minutes that you may read about applies to scheduled triggers, not to this one. Just remember the scenario has to be switched on to receive anything, and test it first with Run once.
04What if a needed Leadinfo module is missing in Make?
It depends on what you need. Leadinfo offers a single trigger in Make and no Make an API Call module, so a scenario cannot fetch, update or search data inside Leadinfo. What it can do is pass each company to modules of other apps, such as a CRM, a spreadsheet or an email tool, and work there. If your use case truly needs more from Leadinfo itself, the team can look at it with you through the help form further down this page.
05Should Leadinfo be automated with Make or n8n?
That depends on your stack. On Make, you get Watch Company, an instant trigger, available from the Free plan, and a visual editor where you add each next step with a click. Make does not give Leadinfo any action or search module, so first check whether n8n offers a Leadinfo node and what it covers. Then pick the platform that already connects the other apps in your flow, such as your CRM. The n8n vs Make comparison linked above lays out the criteria side by side.