How to connect PhantomBuster to Hermes Agent
Connect PhantomBuster to Hermes with ClawLink: paste your PhantomBuster key once and 53 tools work from chat. No MCP server to run, nothing stored on your machine.
PhantomBusterAPI KEYMCPAutomate lead generation and data extraction. Once connected, Hermes Agent can read and act on PhantomBuster from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent PhantomBuster access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical PhantomBuster setup: pair once in the browser and your always-on Hermes agent can act on PhantomBuster for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
Set up ClawLink for Hermes and tell me when it's ready.
1. Install the plugin:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2. Start pairing. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
3. I'll approve it in my browser, then reply "approved".
4. When I say approved, finish setup:
hermes clawlink finish
5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Hermes to PhantomBuster.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect PhantomBuster
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with PhantomBuster?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect PhantomBuster in the ClawLink dashboard — paste your PhantomBuster API key once.
Verify the connection by asking Hermes:
Pull the relevant data from PhantomBuster, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The Hermes 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:
npx -y @useclawlink/cli loginlogin 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.
PhantomBuster MCP for Hermes
Looking for a PhantomBuster MCP server for Hermes Agent? ClawLink connects PhantomBuster to Hermes Agent and exposes 53 PhantomBuster tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw PhantomBuster integration works the same way.
What the Hermes Agent PhantomBuster integration can do
53 PhantomBuster tools are ready for Hermes Agent 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 Hermes
| 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) |
Try it: find the PhantomBuster tool you need
Browse the 30 PhantomBuster tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from PhantomBuster, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from PhantomBuster, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from PhantomBuster, summarize it in plain English, and point out anything that needs attention.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use PhantomBuster
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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.
FAQ
Is there a Hermes Agent PhantomBuster integration?
Yes. ClawLink is the fastest way to connect Hermes to PhantomBuster: link your PhantomBuster account once in the browser and Hermes Agent can call the PhantomBuster API through 53 ready-made tools — no custom code or token handling.
How do I connect PhantomBuster to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect PhantomBuster in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to PhantomBuster in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want PhantomBuster working from chat.
Hermes paired but still can't use PhantomBuster
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
