To connect PhantomBuster with Make, create an API key in your PhantomBuster workspace, then paste it into any PhantomBuster module inside a Make scenario. Once connected, you can automate tasks like launching Phantoms, retrieving output data, and listing your Phantoms directly from Make workflows.
Before you start
To connect PhantomBuster with Make, make sure you have:
- A PhantomBuster account.
- A Make account.
- A valid PhantomBuster API key.
→ If you don't have one, see Create an API key. API keys can only be created by workspace admins - if you don't see the Add API key button, check with your admin.
PhantomBuster Modules in Make.com are blocks that allow you to perform specific actions in a particular application or service. Check available modules in Make's documentation.
Connect PhantomBuster to Make
Once you have your API key, here's how to connect PhantomBuster to Make:
- Log in to your Make account and add any PhantomBuster module to your scenario.
- Click on Create a connection.
- Give your connection a name in the Connection name field (optional).
- In the API Key field, paste your PhantomBuster API key.
- Click Save.
- If prompted, authenticate your account and confirm access.
- You can now build and customize your scenarios and add more PhantomBuster modules.
Build PhantomBuster Scenarios
After connecting PhantomBuster with Make, you can automate tasks by building scenarios with these actions:
Output
Heads up: Outputs are delivered in binary format.
If your scenario sends Phantom output straight to a downstream module that accepts binary (like an HTTP module or a file-storage module), you can use it as-is.
If you need structured data (JSON) - for example, to map fields into a CRM, a database, or a Sheet - you'll need to convert it first.
The fastest way is this Make template. It fetches the binary file from PhantomBuster, parses each row, and writes the rows into a Google Sheet. You can clone it, swap the Sheet for whatever destination you need (HubSpot, Airtable, a webhook, etc.), and keep the parsing logic.
- Watch an Output: Triggers when a Phantom finishes with its recent output.
- Get an Output: Gets the output of the most recent container of a specified Phantom.
- Launch a Phantom: Launches a specified Phantom.
Phantom
- List Phantoms: Retrieves a list of all Phantoms.
- Get a Phantom: Gets metadata of a specified Phantom.
Other
- Download a Result: Downloads the JSON result object associated with a container.
- Make an API Call: Performs an arbitrary authorized API call.
When launching a LinkedIn Phantom, remember to add the browser user agent.
Frequently asked questions
Do I need a paid Make plan to use the PhantomBuster integration?
No, PhantomBuster modules work on any Make plan, but the number of operations per month depends on your Make subscription.
How does this affect my Make plan?
Make charges by operation, and ops can add up fast when scenarios run on large batches of leads or fire frequently. Check your monthly ops counter in Make and consider batching (process more rows per launch, run scenarios less often) before upgrading your plan. For details on how Make counts operations, see Make's documentation on operations.
Where do I find my PhantomBuster API key?
API keys are managed inside your PhantomBuster Workspace and can only be created by Workspace admins. See Create an API key. If you don't see the Add API key button, check with your admin.
What can I do with PhantomBuster modules in Make?
You can watch or get Phantom output, launch a Phantom, list all your Phantoms, get Phantom metadata, download result objects, and make custom API calls.
Why do I need to add a browser user agent when launching a LinkedIn Phantom?
LinkedIn Phantoms require a browser user agent to simulate a real browser session. Without it, the launch may fail.