# How to connect NeverBounce to OpenClaw (paste one key, 12 tools) > Connect NeverBounce to OpenClaw with ClawLink: paste your NeverBounce key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/neverbounce The usual route to NeverBounce 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 NeverBounce setup: install one ClawHub skill, connect NeverBounce in the browser, and OpenClaw can call real NeverBounce actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to NeverBounce. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect NeverBounce** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 neverbounce # connect NeverBounce (browser OAuth) npx -y @useclawlink/cli actions neverbounce # list available actions npx -y @useclawlink/cli run neverbounce --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 NeverBounce in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your NeverBounce API key once. Verify the connection by asking OpenClaw: > Use NeverBounce to account info and walk me through the result in plain English. ### 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 NeverBounce is connected in the dashboard, that agent calls the same 12 NeverBounce 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). ## NeverBounce MCP for OpenClaw Looking for a NeverBounce MCP server for OpenClaw? ClawLink connects NeverBounce to OpenClaw and exposes 12 NeverBounce 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 NeverBounce integration](https://claw-link.dev/hermes/neverbounce) works the same way. ## What the OpenClaw NeverBounce integration can do 12 NeverBounce tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 12. ### 11 of 12 NeverBounce tools for OpenClaw | Tool | What it does | |---|---| | **Account info** `neverbounce_account_info` | Get account information including credits, job counts, and usage statistics | | **Jobs download get** `neverbounce_jobs_download_get` | Download job results as a CSV file via GET | | **Jobs results** `neverbounce_jobs_results` | Retrieve paginated results for a completed job, including original data and verification | | **Jobs status** `neverbounce_jobs_status` | Get the status and progress of a bulk verification job | | **Search jobs** `neverbounce_search_jobs` | Search and list bulk verification jobs in your account with pagination and filtering | | **Single check** `neverbounce_single_check` | Verify a single email address and gather additional information | | **Widget send event** `neverbounce_widget_send_event` | Send widget form events via the JS widget API | | **Confirm poe** `neverbounce_confirm_poe` | Confirm proof of email ownership (POE) from the JavaScript widget | | **Jobs create** `neverbounce_jobs_create` | Create a new bulk verification job with parsing, sampling, and callback options | | **Jobs start** `neverbounce_jobs_start` | Start a parsed job when auto_start is disabled | | **Parse job** `neverbounce_parse_job` | Parse a job created with auto_parse disabled | ## Example prompts **Account Info** > Use NeverBounce to account info and walk me through the result in plain English. **Jobs Download Get** > Use NeverBounce to jobs download get and walk me through the result in plain English. **Jobs Results** > Use NeverBounce to jobs results and walk me through the result in plain English. **Jobs Status** > Use NeverBounce to jobs status and walk me through the result in plain English. ## 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 NeverBounce working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the NeverBounce API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected NeverBounce 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 NeverBounce. | 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 NeverBounce actions to the runtime in a format your agent can reliably use. | 12 tools for NeverBounce are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes NeverBounce 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 NeverBounce in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the NeverBounce 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 NeverBounce skill but can't call the tools The ClawHub skill teaches OpenClaw about NeverBounce, but the calls run through the ClawLink plugin and your connected account. Make sure NeverBounce 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 NeverBounce 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 NeverBounce tools NeverBounce 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 NeverBounce 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. ### NeverBounce 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 NeverBounce has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw NeverBounce integration? Yes. ClawLink is the fastest way to connect OpenClaw to NeverBounce: link your NeverBounce account once in the browser and OpenClaw can call the NeverBounce API through 12 ready-made tools — no custom code or token handling. ### How do I add NeverBounce to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink NeverBounce skill from ClawHub, then you click Connect in the dashboard to authorize NeverBounce. OpenClaw calls the tools from the next message — no config files, and the NeverBounce key you paste is stored server-side instead of in your environment. ### How long does it take to connect NeverBounce to OpenClaw? About two minutes. Sign in, click Connect next to NeverBounce in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring NeverBounce 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 NeverBounce working from chat. ### OpenClaw installed the NeverBounce skill but can't call the tools The ClawHub skill teaches OpenClaw about NeverBounce, but the calls run through the ClawLink plugin and your connected account. Make sure NeverBounce 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 - [OpenClaw ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences