Resources · Make integration

PhantomBuster Make integrationAutomate PhantomBuster with Make.

The PhantomBuster Make integration drops your Phantoms into a scenario, the chain of modules you build in Make. There are 7 in total: 1 trigger, 5 actions and 1 search. An API key is all it takes, no code. The page covers the connection, a first scenario and what each module does.

Try the PhantomBuster integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PhantomBuster Make integration actually do?

PhantomBuster runs the Phantoms. Make runs everything around them. A module is one brick of that chain: a trigger that starts it, an action that does something, a search that goes and fetches a list. Link the two accounts and a Phantom stops being a task someone has to check on, it turns into one step of a process that runs on its own.

Three shapes come back again and again. The first one is reactive: Watch an Output notices that a Phantom has finished, Download a Result pulls the whole result back, and the data keeps moving while nobody is watching the dashboard.

The second one runs on demand. A form comes in, a deal moves to the next stage, and Launch a Phantom starts the right Phantom at that exact second instead of on a fixed rhythm. The third one is housekeeping: List Phantoms hands the scenario every Phantom on the account, and Get a Phantom checks the metadata of one before anything runs, so a scenario confirms what it is about to touch instead of guessing.

What Make does not do here is replace PhantomBuster. The scenario launches, waits, collects and routes; the extraction itself stays on the PhantomBuster side. The Make documentation page for this app is generated from PhantomBuster's own documentation and can contain mistakes, so anything critical gets checked against the source.

The same app also exists as an n8n node. The n8n vs Make comparison lays out the criteria, the PhantomBuster n8n integration page shows the other side, and if nobody on the team has ever built a scenario yet, Make training skips the trial and error of figuring the editor out alone.

Connect

How do you connect PhantomBuster to Make?

  1. 01

    Generate your API key

    PhantomBuster asks for a key before Make can touch anything. Open the workspace settings page from the main navigation menu, generate a new API key, the credential that lets Make talk to your account, and copy what shows up on screen.

  2. 02

    Create the connection from a module

    In Make, drop any PhantomBuster module into a scenario and click Create a connection. A connection is your PhantomBuster account linked to Make once; every PhantomBuster module you add later picks it from a list instead of asking again.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, though a scenario carrying several connections is easier to read when they have names. Paste the key you copied, or follow whatever the window asks for, and confirm.

First scenario

Your first scenario, from the + to the switch

GoalWhen a Phantom finishes with a fresh output, Make downloads the full result and hands it to the next module.

  1. 01

    Create the scenario

    From the Scenarios page, start a new scenario and click the + in the middle of the canvas. That plus sign is where every scenario begins, and it opens the app search.

  2. 02

    Place the trigger

    Type PhantomBuster in the search box and pick Watch an Output. It settles in as the first module, with a small clock on it because Make polls the app instead of waiting for a call.

  3. 03

    Set the trigger up

    Fill in the fields of Watch an Output. Make can only offer what it manages to read on the PhantomBuster side once the connection exists, so create the connection here if it is not done yet.

  4. 04

    Add the action

    Click the + on the right of the trigger and add Download a Result. Map the data the trigger sends into its fields rather than typing values by hand, so the scenario follows whichever Phantom fired.

  5. 05

    Test with Run once

    Click Run once. The scenario executes a single time and every module shows the bundles it received, a bundle being one item travelling from one module to the next. Read them before going further.

  6. 06

    Schedule it and switch it on

    Set the scheduling on the first module. A new scenario sits at every 15 minutes, which is also the floor on the Free plan. Flip the switch and it keeps running without you.

Triggers

What sets the scenario off

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

PhantomBuster1Watch an Output

Watch an Output

Scheduled trigger

In Make“Triggers when a Phantom finishes with its recent output.”

Watch an Output sits at the top of a scenario and reacts once a Phantom has finished and its latest output is there, so everything downstream starts by itself.

How it fires
Make checks the app on the scenario's schedule. This is a scheduled trigger, not an instant one: nothing gets pushed from PhantomBuster, Make goes and looks.
When to use it
a Phantom that runs on its own side, whose results should land in your tools without anyone opening the dashboard.
Watch out
the reaction is never faster than the interval you set, and the Free plan does not go under 15 minutes between two runs.
Modules

What PhantomBuster can do inside a scenario

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

PhantomBuster1

Download a Result

Action

In Make“Downloads the JSON result object associated with a container.”

Download a Result brings back the JSON result object attached to a container, so the raw data lands in the scenario rather than a summary of it.

When to use it
right after a run ends, when the next module needs the whole thing to write rows somewhere.
Watch out
it needs a container to point at, so it belongs after a module that hands one over.
PhantomBuster2

Get an Output

Action

In Make“Gets the output of the most recent container of a specified Phantom.”

Get an Output pulls the output of a Phantom's most recent container, without waiting for anything to happen first.

When to use it
someone launched a Phantom by hand and the scenario has to collect the result a few minutes later.
Watch out
most recent means most recent, an older run stays out of reach from this module.
PhantomBuster3

Get a Phantom

Action

In Make“Gets metadata of a specified phantom.”

Get a Phantom returns the metadata of one Phantom you point at, which is how a scenario checks what it is about to work with.

When to use it
as a first step before a launch, to confirm you are aiming at the Phantom you think you are.
Watch out
reading is all it does, nothing runs until Launch a Phantom says so.
PhantomBuster4

Launch a Phantom

Action

In Make“Launches a specified Phantom.”

Launch a Phantom starts a Phantom you choose, so the moment it runs gets decided inside your scenario.

When to use it
a new contact lands in the CRM and the enrichment has to go now, not at the next fixed slot.
Watch out
starting a run and reading its result are two separate steps, Watch an Output or Get an Output handles the second one.
PhantomBuster5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call sends an authorized request to any endpoint of the PhantomBuster API, through the connection you already created.

When to use it
the six other modules stop short of what you need and the API covers it.
Watch out
you write the call yourself, so the PhantomBuster API reference becomes required reading before the scenario works.
PhantomBuster6

List Phantoms

Search

In Make“Retrieves a list of all Phantoms”

List Phantoms hands the scenario every Phantom on the account, one bundle per Phantom.

When to use it
a scenario that has to sweep the whole list instead of one Phantom whose name you typed in.
Watch out
a search can return zero, one or many bundles, and each bundle makes the following modules run again, one operation counted on your plan every time. Filter early.
Need help

Need help automating PhantomBuster with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the PhantomBuster Make integration free?
Yes, and your Make plan sets the limits. PhantomBuster is a standard app, available from the Free plan, so nothing has to be upgraded to put its modules in a scenario. On that plan you get 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 transfer. Paid plans bring the interval down to 1 minute, remove the cap on active scenarios and count usage in operations per month. The PhantomBuster subscription is a separate matter, handled on their pricing page.
02What do you need to connect PhantomBuster to Make?
Two things: an active PhantomBuster account and an API key. The key is generated from the workspace settings page, which you reach from the main navigation menu, then copied off the screen. On the Make side, add a PhantomBuster module to a scenario, click Create a connection, give it a name in the Connection name field if you want to recognize it later, then paste the credentials or follow the on-screen instructions. That connection is created once and reused by every PhantomBuster module afterwards. No server, no developer, no code.
03Does the PhantomBuster trigger react in real time?
No. Watch an Output is a scheduled trigger, which means Make goes and checks PhantomBuster on the scenario's schedule instead of being told by the app that something happened. An instant trigger would arrive through a webhook, the call an app makes to Make the second an event occurs, and PhantomBuster offers none of those here. So the real delay is the interval you set on the first module: 15 minutes by default on a new scenario, 15 minutes again as the floor on the Free plan, down to 1 minute on a paid plan.
04What if a module is missing or a limit gets in the way?
Reach for Make an API Call. It sends an authorized request to any endpoint of the PhantomBuster API with the connection already in place, which covers what the other six modules leave out. Two things are worth knowing before you dig in. The PhantomBuster page in the Make documentation is generated from PhantomBuster's own documentation and can contain mistakes, so anything important gets confirmed with PhantomBuster directly. And a search module returns several items at once, which changes how many times the rest of the scenario runs.
05Make or n8n for PhantomBuster?
It depends on who will maintain the scenario. Make is a visual editor where the automation gets drawn module by module, which suits a marketing or ops team that wants to build and change things without a developer on hand. n8n sits closer to code, can be self-hosted, and pays off when the automation lives in a technical environment and the team is comfortable there. PhantomBuster exists on both sides, and the module list decides nothing. The useful question is who comes back to fix this once it breaks.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations