# How to connect PhantomBuster to OpenClaw (paste one key, 53 tools) > Connect PhantomBuster to OpenClaw with ClawLink: paste your PhantomBuster key once and 53 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/phantombuster The usual route to PhantomBuster access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical PhantomBuster setup: install one ClawHub skill, connect PhantomBuster in the browser, and OpenClaw can call real PhantomBuster actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/phantombuster ## Setup It takes three steps to connect OpenClaw to PhantomBuster. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect PhantomBuster** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect phantombuster # connect PhantomBuster (browser OAuth) npx -y @useclawlink/cli actions phantombuster # list available actions npx -y @useclawlink/cli run phantombuster --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect PhantomBuster in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your PhantomBuster API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from PhantomBuster, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once PhantomBuster is connected in the dashboard, that agent calls the same 53 PhantomBuster tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## PhantomBuster MCP for OpenClaw Looking for a PhantomBuster MCP server for OpenClaw? ClawLink connects PhantomBuster to OpenClaw and exposes 53 PhantomBuster tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes PhantomBuster integration](https://claw-link.dev/hermes/phantombuster) works the same way. ## What the OpenClaw PhantomBuster integration can do 53 PhantomBuster tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 53. ### 30 of 53 PhantomBuster tools for OpenClaw | Tool | What it does | |---|---| | **Get agent** `phantombuster_get_agent` | Get a PhantomBuster agent by ID | | **Get agent containers** `phantombuster_get_agent_containers` | List PhantomBuster agent containers | | **Get agent output** `phantombuster_get_agent_output` | Get PhantomBuster agent output | | **Get agents fetch all** `phantombuster_get_agents_fetch_all` | List all PhantomBuster agents | | **Get containers fetch all** `phantombuster_get_containers_fetch_all` | List all PhantomBuster containers | | **Get leads by list** `phantombuster_get_leads_by_list` | Get PhantomBuster leads by list | | **Get location ip** `phantombuster_get_location_ip` | Get PhantomBuster location IP | | **Get orgs export agent usage** `phantombuster_get_orgs_export_agent_usage` | Export PhantomBuster agent usage | | **Get orgs fetch** `phantombuster_get_orgs_fetch` | Get PhantomBuster organization info | | **Get orgs fetch agent groups** `phantombuster_get_orgs_fetch_agent_groups` | Get PhantomBuster agent groups | | **Get orgs fetch resources** `phantombuster_get_orgs_fetch_resources` | Get PhantomBuster organization resources | | **Get script** `phantombuster_get_script` | Get a PhantomBuster script | | **Get script by name** `phantombuster_get_script_by_name` | Get a PhantomBuster script by name | | **Get agents fetch deleted** `phantombuster_get_agents_fetch_deleted` | Get deleted agents for the current user or organization | | **Get branches diff** `phantombuster_get_branches_diff` | Get the length difference between the staging and release branch of all scripts | | **Get branches fetch all** `phantombuster_get_branches_fetch_all` | Fetch all branches associated with the current organization | | **Get org storage lists fetch all** `phantombuster_get_org_storage_lists_fetch_all` | Fetch all storage lists for the authenticated organization | | **Get orgs export container usage** `phantombuster_get_orgs_export_container_usage` | Export container usage CSV for current organization | | **Get orgs fetch running containers** `phantombuster_get_orgs_fetch_running_containers` | Get the current organization's running containers | | **Get scripts code** `phantombuster_get_scripts_code` | Get the code of a script | | **Get scripts fetch all** `phantombuster_get_scripts_fetch_all` | Fetch all scripts for the current user | | **Get user** `phantombuster_get_user` | Get information about your PhantomBuster account and your agents using the legacy v1 API | | **Post AI completions** `phantombuster_post_ai_completions` | Request a text completion from the AI module | | **Post hcaptcha** `phantombuster_post_hcaptcha` | Solve an hCaptcha challenge | | **Search company objects** `phantombuster_search_company_objects` | Search company objects in Phantombuster's organizational storage | | **Search lead objects** `phantombuster_search_lead_objects` | Search lead objects in Phantombuster org storage | | **Post branches create** `phantombuster_post_branches_create` | Create a new branch | | **Post identities generate token** `phantombuster_post_identities_generate_token` | Generate an identity token for PhantomBuster | | **Post org storage leads save many** `phantombuster_post_org_storage_leads_save_many` | Save multiple leads (1-20) to organization storage in a single batch operation (Beta) | | **Post recaptcha** `phantombuster_post_recaptcha` | Solve a reCAPTCHA challenge (v2 or v3) | ## Example prompts **Get Agent** > Pull the relevant data from PhantomBuster, summarize it in plain English, and point out anything that needs attention. **Get Agent Containers** > Pull the relevant data from PhantomBuster, summarize it in plain English, and point out anything that needs attention. **Get Agent Output** > Pull the relevant data from PhantomBuster, summarize it in plain English, and point out anything that needs attention. **Get Agents Fetch All** > Pull the relevant data from PhantomBuster, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want PhantomBuster working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the PhantomBuster API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected PhantomBuster account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for PhantomBuster. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right PhantomBuster actions to the runtime in a format your agent can reliably use. | 53 tools for PhantomBuster are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes PhantomBuster to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect PhantomBuster in the browser, and the 53 tools above work from chat. There is no SDK and no config file, and the PhantomBuster key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the PhantomBuster skill but can't call the tools The ClawHub skill teaches OpenClaw about PhantomBuster, but the calls run through the ClawLink plugin and your connected account. Make sure PhantomBuster is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect PhantomBuster from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling PhantomBuster tools PhantomBuster tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every PhantomBuster call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### PhantomBuster returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for PhantomBuster has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw PhantomBuster integration? Yes. ClawLink is the fastest way to connect OpenClaw to PhantomBuster: link your PhantomBuster account once in the browser and OpenClaw can call the PhantomBuster API through 53 ready-made tools — no custom code or token handling. ### How do I add PhantomBuster to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink PhantomBuster skill from ClawHub, then you click Connect in the dashboard to authorize PhantomBuster. OpenClaw calls the tools from the next message — no config files, and the PhantomBuster key you paste is stored server-side instead of in your environment. ### How long does it take to connect PhantomBuster to OpenClaw? About two minutes. Sign in, click Connect next to PhantomBuster in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring PhantomBuster up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want PhantomBuster working from chat. ### OpenClaw installed the PhantomBuster skill but can't call the tools The ClawHub skill teaches OpenClaw about PhantomBuster, but the calls run through the ClawLink plugin and your connected account. Make sure PhantomBuster is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [HubSpot](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Salesforce](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows