How to Send Your Phantom Results to Make in Real Time Using a Webhook

Sophie
Sophie This badge shows you’re hearing straight from the source! Team members are here to share insider tips, answer questions, and guide you through PhantomBuster with expert knowledge. They’re dedicated to helping you succeed and making sure your automation journey feels easy and exciting. PhantomBuster Official
  • Updated

To send your Phantom's results to Make automatically, create a custom webhook in a Make scenario, copy its URL, and paste it into your Phantom's Advanced settings → Webhooks in PhantomBuster. Every time the Phantom runs, its results are pushed straight to Make, where a Parse JSON module turns them into structured fields you can use.

Before you start

  • The Phantom you want to use is already created and set up in your PhantomBuster workspace. This method receives an existing Phantom's output, it doesn't launch or configure the Phantom from Make.
  • You have a Make account. No PhantomBuster API key is needed for the webhook method, the webhook URL is all that connects the two.

Webhook vs. Download a Result: a webhook pushes results to Make automatically every time the Phantom finishes. If you'd rather pull a specific past run on demand, use the Download a Result module method instead.

Step 1: Create a custom webhook in Make

  1. In a new Make scenario, add the Webhooks → Custom webhook module.
  2. Click Add, give the webhook a name (e.g. My gateway-webhook), and save. Make generates a unique URL, click Copy address to clipboard.
Make Custom webhook module showing the generated URL and Copy address to clipboard.

Step 2: Paste the webhook URL into your Phantom's advanced settings

  1. In your PhantomBuster Dashboard, find the Phantom, click the three-dots menu, and select Setup.
  2. Scroll to Advanced settings and open the Webhooks tab. See How to Use Advanced Settings for Phantoms and Workflows for more details.
  3. Paste the URL into the Custom webhook URL field and click Save settings.
Phantom Advanced settings → Webhooks tab with the Make URL in the Custom webhook URL field

Step 3: Set Make to listen, then launch the Phantom

  1. Back in Make, run the scenario once. The webhook module shows "Waiting for data…".
    Make Custom webhook module showing "Waiting for data…"
  2. In PhantomBuster, launch the Phantom. When it finishes, its results are sent to Make automatically. The webhook receives the run's data, including the resultObject (your leads).
    Make webhook output showing agentName, containerId, and resultObject

Step 4: Parse the results into structured fields

The webhook payload arrives as raw JSON, so add a Parse JSON module to make the fields readable.

  1. Add a Parse JSON module and set its JSON string to the resultObject from the webhook.
    Parse JSON module with JSON string mapped to resultObject
  2. Run once. You'll now see individual fields like firstName, lastName, companyName, and linkedinCompanyUrl - ready to map into any downstream module (a CRM, Google Sheets, Airtable, etc.).
    Parse JSON output showing structured fields

From here you can add any destination module and map these fields - see How to Send Your Phantom Results to Airtable (or Any CRM) Using Make for the mapping steps.

Troubleshooting

  • No data arrives in Make: confirm the Phantom completed its run, and that the webhook URL in the Phantom's advanced settings matches the one Make generated (no typos).
  • Fields look like one big blob of text: add or re-check the Parse JSON module, it should point at the webhook's resultObject.
  • Data stops arriving after editing the scenario: re-copy the webhook URL, and update the Phantom's advanced settings.

Frequently asked questions

How do I send PhantomBuster results to Make automatically?

Create a custom webhook in Make, copy its URL, and paste it into your Phantom's Advanced settings → Webhooks. Results are pushed to Make each time the Phantom runs.

Do I need a PhantomBuster API key for the webhook method?

No. The webhook URL is all that's needed, no API connection required.

Why do the results arrive as raw JSON?

The webhook sends the full payload as JSON. Add a Parse JSON module in Make, pointed at the resultObject, to break it into individual fields.

What's the difference between the webhook and the Download a Result module?

The webhook pushes results automatically in real time; Download a Result lets you pull a chosen past run on demand.

Was this article helpful?

0 out of 0 found this helpful