Built by Metorial, the integration platform for agentic AI.
Add a Phantom to the launch queue with optional custom arguments. The Phantom must already be set up in your PhantomBuster workspace. Returns a container ID to track the asynchronous execution. Launches can use paid runtime and perform external actions configured in the Phantom.
Retrieve details about a specific Phantom execution (container) including its status, console output, exit message, and result data. Use a container ID from a launch or from the execution history.
Abort a currently running Phantom execution. Stops all running instances of the specified Phantom.
Manage lead lists in the LinkedIn Leads database. Fetch all lists, get a specific list, create/update a list, or delete a list. - **fetchAll**: Get all lists in the workspace. - **fetch**: Get a specific list by ID. - **save**: Create or update a list. - **delete**: Delete a list by ID.
Retrieve the latest output from a Phantom including its current status, console output, progress, and result object. Useful for checking the state of a running or recently completed Phantom.
Fetch, save, or delete leads in the LinkedIn Leads database. - **Fetch**: Retrieve leads from a specific list by providing a `listId`. - **Save**: Add or update one or more leads by providing the `leads` array. - **Delete**: Remove leads by providing `leadIdsToDelete`.
Retrieve information about your PhantomBuster workspace (organization), including its identity and any plan or resource details returned by the provider.
List all Phantoms (automation agents) in your workspace. Returns each Phantom's configuration, status, and scheduling information. Use this to discover available Phantoms and their IDs for launching or managing them.
Permanently delete a Phantom from your workspace. This action cannot be undone.
Retrieve detailed information about a specific Phantom by its ID, including configuration, script, proxy settings, storage paths, and last execution status.
Prepare an accumulated Phantom result file as a downloadable CSV or JSON. These files combine results across launches, rather than one container. The Phantom must already have produced the requested file. Use Get Execution for launch-specific result data.
Create or update an individual Phantom. Provide phantomId to update; creation requires a name and either an existing scriptId or an exact script name. Current public templates use scriptOrg "phantombuster" and branch "master". This does not launch the Phantom; scheduling and notification settings can have external effects.
List execution history (containers) for a specific Phantom. Returns status, timing, and exit information for each run. Useful for monitoring and debugging Phantom performance.