Integration · Sell and serve

PhantomBuster and Meteor AI agents

Connect PhantomBuster to a Met: check your Phantoms, pull their results and build filtered lead lists from WhatsApp with the official MCP.

Book a demo See every integration

How do I use PhantomBuster from WhatsApp to build prospect lists?

With the PhantomBuster ready connector, your Met works in the PhantomBuster workspace you pick when connecting. It finds your Phantoms, checks whether the last run finished and pulls their results, so you can ask on WhatsApp how many prospects this week's LinkedIn search found. It also searches your stored leads with filters, builds dynamic lists from them and saves new leads. Creating or adjusting a Phantom and launching it start switched off: it only does them if the admin turns those actions on. It is PhantomBuster's official server: usage runs on your plan, and delete actions also start switched off.

What it automates

What a Meteor Met does with PhantomBuster

Ask on WhatsApp what a Phantom found

You ask the Met how many prospects this week's LinkedIn export brought in. The Met finds the Phantom, checks whether the last run finished well and summarizes its result: how many rows, which job titles and which cities.

Build a prospect list with a filter

You ask for "the managers in Bogotá that came from that Phantom". The Met tests the filter on your stored leads, tells you how many match with examples and, once you confirm, saves the dynamic list and checks how many members it ended up with.

Check why a run failed

If a Phantom brought nothing, the Met reads its run log and tells you the first error, for example that the LinkedIn account got disconnected, instead of launching it again.

Save contacts that come in some other way

If a salesperson sends you LinkedIn profiles on WhatsApp, the Met saves them as leads in your workspace, up to 20 per call, so they join your lists.

22 tools

Everything your Met can ask PhantomBuster for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`orgs_fetch`	Returns the connected workspace, its time zone and its plan's limits.
`agents_fetch_all`	Lists the workspace's Phantoms, with filters to avoid huge responses.
`agents_fetch`	Opens a Phantom with its configuration and, when asked, its field manifest.
`agents_fetch_deleted`	Lists deleted Phantoms, so they are not confused with a live one of the same name.
`agents_save`	Creates a Phantom from a store script or updates its configuration and schedule. It starts switched off.
`agents_launch`	Launches a Phantom run. It starts switched off.
`agents_fetch_output`	Brings a Phantom run's status and log, incrementally.
`agents_delete`	Permanently deletes a Phantom and its results. It starts switched off.
`agents_unschedule_all`	Removes the schedule from every Phantom in the workspace at once. It starts switched off.
`containers_fetch`	Checks a single Phantom run and its status.
`containers_fetch_result_object`	Brings a Phantom's latest structured result.
`scripts_fetch_all`	Lists scripts, including the PhantomBuster store ones, with filters.
`scripts_fetch`	Opens a script with the fields its configuration asks for.
`identities_search`	Searches the connected accounts, such as LinkedIn, that Phantoms run as.
`identities_generate_token`	Generates a link for an account owner to connect it to the workspace. It starts switched off.
`org_storage_lists_fetch_all`	Lists the lead lists saved in the workspace.
`org_storage_lists_save`	Creates a lead list from a filter, or updates an existing one.
`org_storage_lists_delete`	Deletes a lead list without deleting the leads in it. It starts switched off.
`org_storage_leads_objects_search`	Searches stored leads with a filter, useful to test it before saving a list.
`org_storage_leads_by_list_listid`	Reads a lead list's members and how many there are.
`org_storage_leads_save_many`	Saves new leads in the workspace, up to 20 per call.
`org_storage_filter_help`	Returns the full reference of the filters lead lists accept.

The limits

What the PhantomBuster integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask for confirmation in the chat before writing or launching. The admin chooses in Connections which actions stay on; launching, saving a Phantom and delete actions start switched off.
It does not work across more than one workspace: it acts only in the one you picked when connecting, and switching means reconnecting.
It does not protect your LinkedIn account for you. Platforms limit automation, and launching too much or too often can restrict or suspend the account the Phantom runs as.
It does not take a CSV file as a Phantom's input. Input goes as a Google Sheets link, a lead list or another Phantom's results.
Deleting a Phantom permanently deletes its results. Deleting a list does not delete the leads in it.

Before you start

What you need to connect PhantomBuster

1

A PhantomBuster account with its accounts connected

Your business's PhantomBuster account, with the LinkedIn or other network accounts already connected through the PhantomBuster extension. Usage runs on your plan; Meteor does not resell PhantomBuster.
2

Connect it in Met

In Met, open Connections → PhantomBuster → Connect. A PhantomBuster window opens so you can sign in, pick the workspace and authorize Met. Launching, saving a Phantom and deleting start switched off: the admin decides which ones to turn on.

Frequently asked questions

Questions about PhantomBuster and Meteor

Only if the admin turns on the launch action, which starts switched off. Saving a change launches nothing: launching is a separate action. Since each launch acts with your LinkedIn or other network account, it is worth deciding carefully whether to turn it on.

Only if the admin turns those actions on, because they start switched off. Deleting a Phantom deletes its results for good; deleting a list keeps the stored leads.

Yes. A list is a saved filter over your leads: any new lead that matches the filter, from whichever Phantom, joins the list.

Each connection works in a single one. If you serve several clients with separate workspaces, each one needs its own connection.

Step by step