PhantomBuster is useful when teams need repeatable extraction and workflow automation, but the real friction starts after the run finishes: checking what succeeded, figuring out what changed, and deciding which records are worth acting on. A PhantomBuster AI assistant is most useful when it helps the team monitor agent health, review extracted output, summarise large exports, and turn raw Phantom results into clean outbound or research follow-up from Slack.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like PhantomBuster — it's considerably more involved.
Connecting OpenClaw with PhantomBuster: Step by Step
Step 1: Get Your PhantomBuster API Key
Log into PhantomBuster and go to your profile → API. Copy your API key. The PhantomBuster API base URL is https://api.phantombuster.com/api/v2/. Authenticate with the key in the X-Phantombuster-Key header.
Step 2: List and Monitor Your Agents
The /agents/fetch-all endpoint returns all your configured Phantoms with their IDs and last run status. /agents/fetch-output lets you retrieve the output data from a completed run. /agents/launch triggers a Phantom to run on demand — useful for triggering scrapes from a Slack command.
Step 3: Build the Proxy and Skill File
Build your proxy around agent status and output retrieval. Write ~/.openclaw/skills/phantombuster.md listing your most-used Phantoms by name and agent ID, what they extract, and how often they run. This lets your team ask "what did the LinkedIn company scraper find today?" and get a real answer.
Challenges and Caveats
Phantoms Run on PhantomBuster's Infrastructure
PhantomBuster Phantoms run on PhantomBuster's servers, not yours. The API gives you control and visibility, but execution happens externally. If a Phantom fails due to platform changes (LinkedIn blocking the scraper, for example), you'll see failure status in the API but resolution is in the PhantomBuster dashboard.
Output Size Can Be Large
Some Phantoms extract thousands of rows. Pulling full output into a Slack message isn't practical — your skill file should instruct Claude to summarise or filter output rather than dump raw data.
Skip All of This — Use Cody Instead
Cody gives your team a PhantomBuster AI assistant in Slack, so people can monitor agent runs, review extracted output, compare recent exports, and turn Phantom results into actionable follow-up without building their own control surface for run status and data triage.
Related Guides
- Connecting OpenClaw with Apollo: A Practical Guide
- Connecting OpenClaw with Clay: A Practical Guide
- Connecting OpenClaw with Linkedin: A Practical Guide
Need the model-flexible version? See: How to Connect PhantomBuster to OpenClaw: Setup, Models, and Workflow Guide.