Resources · Make integration

PredictLeads Make integrationAutomate PredictLeads with Make.

Your lead list already has names; PredictLeads can add the signals behind each company. The PredictLeads Make integration offers 23 modules (6 actions, 17 searches) for sales and growth teams. This page shows how to connect your account and build a first enrichment scenario.

Try the PredictLeads integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PredictLeads Make integration do for you?

The PredictLeads Make integration lets a Make scenario (the automation you build, a chain of steps) ask PredictLeads about a company and pass the answer to your other tools. Each step is a module, one brick of the scenario. Every item a module returns travels on as a bundle: one company, one job opening, one news event.

Enrich an account before the first call. A company lands in your lead list, Get a Company pulls its PredictLeads record, and Search Company Technologies adds the tools it runs. Your rep opens a CRM row that already says something.

Spot hiring as a buying signal. Search Company Job Openings returns the postings of one company, so a growth team can route accounts that are hiring into a dedicated sequence. Search Company Financing Events plays the same role for funding news.

Build a lookalike list. Start from your best customer and run Search Company Similar Companies, then drop each result into a sheet for review.

A fair warning: the Make doc for this app is thin. It says complete documentation is not available yet and describes none of the modules, so this page reads each one by its name. Test every module with Run once before you rely on its output. PredictLeads also offers no trigger in Make, which means your scenario starts from another app or from a schedule. If you are new to the editor, the Make training covers the basics, Make pricing explains how operations are counted, and n8n vs Make helps if you hesitate between the two tools.

Connect

How do you connect PredictLeads to Make?

  1. 01

    Add a PredictLeads module

    In your scenario, click the +, search for PredictLeads and pick any module, for example Get a Company. Then click Create a connection. A connection is your PredictLeads account linked to Make once and reused by every PredictLeads module.

  2. 02

    Name the connection

    This step is optional, but a clear name such as "PredictLeads sales team" saves confusion later, when several people or several accounts share the same Make organization and you need to know which one a module uses.

  3. 03

    Authorize and save

    Depending on what PredictLeads asks for, either approve access on the PredictLeads page that opens, or paste the key PredictLeads gives you. Click Save. The Make doc gives no app-specific step here, so follow the generic flow.

First scenario

Your first scenario with PredictLeads

GoalWhen a new company reaches your lead source, Make pulls its PredictLeads record and lists the job openings it has published.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module is the app where your companies arrive, such as a sheet or a CRM, since PredictLeads has no trigger.

  2. 02

    Add Get a Company

    Click the + on the right of that first module, search for PredictLeads and choose Get a Company. Create the connection if you have not done it yet.

  3. 03

    Map the company

    Fill the module fields by mapping the company from the first module. Make shows the data it received from that module, so you click the value instead of typing it.

  4. 04

    Add the job search

    Click the + again and add Search Company Job Openings. Map the same company. This search can return zero, one or several openings, each as its own bundle.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Read them now: it is the only reliable way to learn what PredictLeads sends back.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (a new scenario runs every 15 minutes by default, and 15 minutes is also the minimum interval on the Free plan), then switch the scenario on.

Modules

What each PredictLeads module does

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

PredictLeads1

Get a Company

ActionIn the docs only

Get a Company gives your scenario one company from PredictLeads as a single bundle, ready to map into a CRM record, a sheet row or a message to your team.

When to use it
right after a new account appears in your lead source, to open the file with context instead of a bare name.
Watch out
the doc lists no field for this module, so run it once and read the bundle before mapping.
PredictLeads2

Get a Job Opening

ActionIn the docs only

You get the details of one job opening, alone in its bundle, so the next module can quote the role in a note or an alert.

When to use it
you already hold a posting from a job search and want to handle that single posting in a separate branch of the scenario.
Watch out
as an action it works on one opening at a time; to list several, use a search module instead.
PredictLeads3

Get a News Event

ActionIn the docs only

One news event about a company, fetched as its own bundle, becomes material for a rep: a short line in the CRM or a message in the channel of the account owner.

When to use it
a news search has surfaced an event and you want to act on that one event only.
Watch out
the Make doc describes nothing of what an event contains, so check the output with Run once first.
PredictLeads4

Get a Product

ActionIn the docs only

This action returns a single product known to PredictLeads, which helps when a pitch depends on what the prospect actually sells.

When to use it
a product search pointed to one offer and your account executive wants it on the deal before the demo.
Watch out
it works on one product; if you need the whole catalog of a company, Search Company Products is the better pick.
PredictLeads5

Get a Technology

ActionIn the docs only

Get a Technology brings back one technology as PredictLeads records it, so you can store a clean reference next to the accounts that use it.

When to use it
you build a list around one tool your product replaces and need that tool as a record before searching who runs it.
Watch out
one technology per run; the list of tools of a company comes from Search Company Technologies.
PredictLeads6

List API subscription information

SearchIn the docs only

Reading your own PredictLeads subscription from inside Make is what this search offers, which is handy to keep an eye on your API plan without leaving the editor.

When to use it
before a large enrichment batch, to check what your subscription allows and stop the scenario if needed.
Watch out
the doc does not say which values come back; read them with Run once before you build a filter on them.
PredictLeads7

Make an API Call

ActionIn the docs only

With Make an API Call, any endpoint of the PredictLeads API becomes reachable from your scenario, using the connection you already created.

When to use it
the other PredictLeads modules do not cover the request you need, and you know the endpoint from the PredictLeads API documentation.
Watch out
you write the request yourself, so the path and parameters come from that API documentation, not from Make.
PredictLeads8

Search Companies

SearchIn the docs only

Search Companies turns PredictLeads into a prospect finder: it returns zero, one or several companies, each as its own bundle for the modules that follow.

When to use it
you want to feed a fresh list of accounts into a sheet or a CRM rather than enrich names you already have.
Watch out
every returned company runs the next modules once, and each run is an operation counted on your plan.
PredictLeads9

Search Companies using Technology

SearchIn the docs only

Here the question is reversed: you start from a technology and get back the companies that use it, one bundle per company.

When to use it
your product integrates with a given tool, and sales wants every account running that tool in a target list.
Watch out
a popular technology can return many companies; test with Run once and add a filter before the scenario writes anything.
PredictLeads10

Search Company Connections

SearchIn the docs only

Links between one company and other organizations, as PredictLeads records them, come back as a list you can route to your account map.

When to use it
you prepare an account plan and want to see which other companies are tied to the prospect.
Watch out
the doc does not define what counts as a connection, so read a few results before building on them.
PredictLeads11

Search Company Financing Events

SearchIn the docs only

Funding news is often the best reason to call, and this search lists the financing events PredictLeads holds for one company.

When to use it
you want accounts that just raised money flagged in the CRM so the owner can reach out with a relevant angle.
Watch out
the search may return nothing for a company; plan what the scenario does when no bundle comes out.
PredictLeads12

Search Company Github Repositories

SearchIn the docs only

Engineering-led prospects show their stack in public code, and this search returns the GitHub repositories tied to one company.

When to use it
you sell a developer tool and want the rep to see what the prospect's engineers publish before a technical call.
Watch out
a company with many repositories sends many bundles, so each step after it costs more operations.
PredictLeads13

Search Company Job Openings

SearchIn the docs only

Hiring tells you where a company invests. This search returns the job openings of one company, each opening as a separate bundle.

When to use it
a target account posts roles in the team your product serves, and you want that signal next to the deal.
Watch out
to handle all openings in one message, add an aggregator after the search, otherwise each opening triggers its own message.
PredictLeads14

Search Company News Events

SearchIn the docs only

A list of news events about one company gives your team talking points drawn from what actually happened to the account.

When to use it
an opportunity moves to a new stage and the owner wants recent context before the next meeting.
Watch out
the doc gives no detail on event types, so check the bundles with Run once and filter on what you find.
PredictLeads15

Search Company Products

SearchIn the docs only

What a prospect sells shapes the pitch, and this search returns the products PredictLeads associates with one company.

When to use it
your offer fits only certain product lines, and you want to qualify an account on that before booking a demo.
Watch out
for one product in depth, pass its result to Get a Product rather than running the whole search again.
PredictLeads16

Search Company Similar Companies

SearchIn the docs only

Lookalike prospecting starts here: give it one company and it returns companies PredictLeads considers similar, one bundle each.

When to use it
a customer just signed and you want accounts that resemble it added to a list for outbound.
Watch out
check that each result is not already a customer before writing it to your CRM, or you will create duplicates.
PredictLeads17

Search Company Technologies

SearchIn the docs only

The tools a company runs, as detected by PredictLeads, come back from this search so your rep knows the prospect's environment.

When to use it
you qualify leads on the software they already use, for example a competitor your product replaces.
Watch out
it starts from one company; to go from one tool to many companies, Search Companies using Technology is the module.
PredictLeads18

Search Company Website Evolution

SearchIn the docs only

Changes on a company website can hint at a new offer or a repositioning, and this search returns that history for one company.

When to use it
an account manager watches a strategic customer and wants website changes logged in the account file.
Watch out
the doc says nothing about what a change contains; read the bundles once before you map them.
PredictLeads19

Search Job Openings

SearchIn the docs only

Unlike the company-level search, this one looks across job openings in general and returns each match as its own bundle.

When to use it
you look for any company hiring for a role linked to your product, without a list of accounts to start from.
Watch out
a wide search can return many openings; test with Run once and narrow it before switching the scenario on.
PredictLeads20

Search Latest Posts

SearchIn the docs only

Recent posts known to PredictLeads come back as a list you can push into a feed, a sheet or a team channel.

When to use it
your marketing team wants fresh material about target accounts in one place without opening several sites.
Watch out
the doc does not say what a post is or where it comes from, so read the results before you publish anything from them.
PredictLeads21

Search Portfolio Companies

SearchIn the docs only

Going by its name, this search returns the companies of a portfolio, each as a bundle, which opens prospecting through investors.

When to use it
one investor backs several of your customers and you want the rest of its portfolio in a target list.
Watch out
the Make doc does not describe this module; confirm with Run once that the output matches what you expect.
PredictLeads22

Search Products

SearchIn the docs only

Instead of starting from one company, this search looks across products and returns every match as a separate bundle.

When to use it
you target companies that sell a certain kind of product and need the list before any enrichment.
Watch out
each result runs the modules that follow, so filter early to keep your operation count under control.
PredictLeads23

Search tracked Technologies

SearchIn the docs only

The catalog of technologies PredictLeads follows is what this search lists, useful to pick the exact tool name before you query companies.

When to use it
you set up a technology-based list and want to confirm the tool is tracked before building the rest of the scenario.
Watch out
store the result in a sheet you can reuse instead of calling this search in every run.
Need help

Need help automating PredictLeads with Make?

A person reads every message.

FAQ

Questions about the PredictLeads Make integration

01Is the PredictLeads Make integration free?
Yes, on the Make side. PredictLeads is a standard app, so its modules work on the Free plan, which allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run 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. Make counts operations, one module running on one bundle, against your plan. Your PredictLeads subscription is a separate matter this page does not cover.
02What do you need to connect PredictLeads to Make?
A PredictLeads account and a Make account. The Make doc lists no prerequisite and no app-specific connection step, so the generic flow applies: add a PredictLeads module, click Create a connection, give it a name if you like, then either approve access on the PredictLeads page or paste the key PredictLeads provides, and click Save. The connection is created once and every PredictLeads module in your scenarios reuses it. Test right after with Run once, since the doc offers no troubleshooting section.
03Does PredictLeads have a trigger in Make?
No. Its 23 modules are 6 actions and 17 searches, so nothing in PredictLeads starts a scenario by itself. Two options remain. Start with a trigger from another app, for example the app where new leads arrive, and let PredictLeads enrich each one. Or rely on scheduling: the clock on the first module runs the scenario at a set interval, every 15 minutes by default. A scheduled start means Make checks at that interval; an instant trigger, where an app calls Make through a webhook, is not available here.
04What if a PredictLeads module is missing in Make?
Use Make an API Call. This module can reach any endpoint of the PredictLeads API with the connection you already set up, so a request not covered by the other modules is still possible. You write the path and parameters yourself, from the PredictLeads API documentation. Keep in mind that the Make doc for this app is incomplete: it states that full documentation is not available yet. Test each module and each custom call with Run once and read the bundles before you build further steps on them.
05Should you use Make or n8n with PredictLeads?
It depends on which tool your team already works in. Make gives PredictLeads 23 ready modules plus Make an API Call, and it runs on every plan including Free. Apps like PredictLeads often have a node in n8n as well, so check its node list before deciding. Neither tool is ranked here; the choice comes down to the editor you prefer, the other apps in your scenarios and your plan. The n8n vs Make comparison linked above lays out the differences between the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations