To launch a Phantom from Make without writing any JSON, add the PhantomBuster Launch a Phantom module to your scenario, connect your PhantomBuster account, and select the Phantom by its Phantom ID. This is the simplest way to trigger a Phantom from Make. For full control over the launch input, use the Make an API Call module method instead.
Before you start
- The Phantom you want to launch is already created and set up in your PhantomBuster workspace. With this module you're triggering an existing Phantom, you can't create or configure the Phantom itself from Make.
- You have a valid PhantomBuster API key to create the connection.
→ 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.
Workflows (like LinkedIn Search to Lead Connection) can't be launched via API or Make. Chain individual Phantoms instead.
Step 1: Add the "Launch a Phantom" module
In your Make scenario, add a PhantomBuster module. In the module list you'll see actions grouped under Output and Phantom, select Launch a Phantom.
Step 2: Connect your PhantomBuster account
The first time you use a PhantomBuster module, you'll need to create a connection.
- In the module's Connection field, click Create a connection.
- Give the connection a name (e.g. My PhantomBuster connection), paste your PhantomBuster API key into the API Key field, and click Save.
Already connected PhantomBuster to Make? Just pick your existing connection from the dropdown.
Step 3: Select the Phantom to launch
With the connection selected, enter the Phantom ID of the Phantom you want to run.
- To find it, open the Phantom's console in PhantomBuster and copy the long number in the browser URL between /phantoms/ and /console. See How to find your Agent ID for API calls for more details.
Step 4: Run it and check the result
Click Run once. On success, the module's output shows a Container ID - the ID of the run you just triggered.
You can then track results in your PhantomBuster workspace.
Troubleshooting
- Nothing launches / error: confirm the connection's API key is valid and the Phantom ID is correct.
- "[404] Agent not found": the Phantom ID is wrong or belongs to another Workspace, see How to Fix the "[404] Agent not found" Error.
- LinkedIn Phantom launches but fails: its stored session cookie may be expired. Confirm the Phantom runs when launched manually in PhantomBuster first. If you need to pass a fresh cookie per launch, use the Make an API Call method.
Frequently asked questions
How do I launch a Phantom from Make?
Add the Launch a Phantom module, connect your PhantomBuster account, and enter the Phantom's ID.
What's the difference between "Launch a Phantom" and "Make an API Call"?
Launch a Phantom is the simple, no-code option, you just give it a Phantom ID. Make an API Call lets you send custom input (like a session cookie or changed parameters) per launch.
Where do I find my Phantom ID?
In the Phantom's console URL: the long number between /phantoms/ and /console.
Can I launch a Workflow from Make?
No. Workflows can't be launched via API or Make. Chain individual Phantoms instead.