# PhantomBuster integrations: agents and containers

> Start a Tray.ai workflow when PhantomBuster sends “Agent run finished”. Connect PhantomBuster to the rest of your sales stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/phantombuster-integrations/
**Categories:** Sales
**Connects through:** HTTP Connector

## Overview

PhantomBuster runs cloud automations that collect lead and profile data from websites and social networks, then export or push the results to other tools. Tray.ai connects to PhantomBuster through the HTTP Connector, so your workflows can call the PhantomBuster API alongside the rest of your stack.

## Use cases

### Agents

Read, create, update, and delete agents in PhantomBuster from any Tray.ai workflow. The PhantomBuster API covers calls such as launch an agent and stop an agent.

- Launch an agent
- Stop an agent
- Get agent output

### Containers

Read containers in PhantomBuster from any Tray.ai workflow. The PhantomBuster API covers calls such as list containers and get a container.

- List containers
- Get a container
- Get container output

### Leads

Read, create, and delete leads in PhantomBuster from any Tray.ai workflow. The PhantomBuster API covers calls such as save a lead and save many leads.

- Save a lead
- Save many leads
- Delete many leads

### Scripts

Read, create, and delete scripts in PhantomBuster from any Tray.ai workflow. The PhantomBuster API covers calls such as list scripts and get a script.

- List scripts
- Get a script
- Save a script

## Challenges Tray.ai solves

### Keeping PhantomBuster credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store PhantomBuster credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the PhantomBuster API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the PhantomBuster API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to PhantomBuster?

Yes. Tray.ai connects to PhantomBuster through the HTTP Connector, which calls the PhantomBuster API directly. Any call the PhantomBuster API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with PhantomBuster?

The PhantomBuster API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated PhantomBuster connector?

PhantomBuster runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated PhantomBuster connector from the PhantomBuster API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/
