# How to connect Verifiedemail to OpenClaw (paste one key, 9 tools) > Connect Verifiedemail to OpenClaw with ClawLink: paste your Verifiedemail key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/verifiedemail The usual route to Verifiedemail 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 Verifiedemail setup: install one ClawHub skill, connect Verifiedemail in the browser, and OpenClaw can call real Verifiedemail 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 Verifiedemail. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Verifiedemail** — 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 verifiedemail # connect Verifiedemail (browser OAuth) npx -y @useclawlink/cli actions verifiedemail # list available actions npx -y @useclawlink/cli run verifiedemail --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 Verifiedemail in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Verifiedemail API key once. Verify the connection by asking OpenClaw: > Use Verifiedemail to check credits 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 Verifiedemail is connected in the dashboard, that agent calls the same 9 Verifiedemail 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). ## Verifiedemail MCP for OpenClaw Looking for a Verifiedemail MCP server for OpenClaw? ClawLink connects Verifiedemail to OpenClaw and exposes 9 Verifiedemail 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 Verifiedemail integration](https://claw-link.dev/hermes/verifiedemail) works the same way. ## What the OpenClaw Verifiedemail integration can do 9 Verifiedemail tools are ready for OpenClaw once the account is connected. ### All 9 Verifiedemail tools for OpenClaw | Tool | What it does | |---|---| | **Check credits** `verifiedemail_check_credits` | Retrieve the remaining verification credits | | **Check file status** `verifiedemail_check_file_status` | Check the status of a previously uploaded file | | **Get entitlements** `verifiedemail_get_entitlements` | Retrieve information about available credits across different entitlement types | | **Get shared credentials** `verifiedemail_get_shared_credentials` | Retrieve a list of shared credential IDs | | **Get1 click user data** `verifiedemail_get1_click_user_data` | Retrieve data for a user who has completed a 1-Click Signup flow | | **List downloads** `verifiedemail_list_downloads` | Get a list of previously created download requests | | **List lists** `verifiedemail_list_lists` | Get all email lists in your account | | **Verify email** `verifiedemail_verify_email` | Verify the deliverability and validity of an email address | | **Post1 click credentials update** `verifiedemail_post1_click_credentials_update` | Update 1-Click credentials | ## Example prompts **Check Credits** > Use Verifiedemail to check credits and walk me through the result in plain English. **Check File Status** > Use Verifiedemail to check file status and walk me through the result in plain English. **Get Entitlements** > Pull the relevant data from Verifiedemail, summarize it in plain English, and point out anything that needs attention. **Get Shared Credentials** > Pull the relevant data from Verifiedemail, 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 Verifiedemail working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Verifiedemail API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Verifiedemail 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 Verifiedemail. | 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 Verifiedemail actions to the runtime in a format your agent can reliably use. | 9 tools for Verifiedemail are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Verifiedemail 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 Verifiedemail in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Verifiedemail 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 Verifiedemail skill but can't call the tools The ClawHub skill teaches OpenClaw about Verifiedemail, but the calls run through the ClawLink plugin and your connected account. Make sure Verifiedemail 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 Verifiedemail 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 Verifiedemail tools Verifiedemail 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 Verifiedemail 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. ### Verifiedemail 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 Verifiedemail has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Verifiedemail integration? Yes. ClawLink is the fastest way to connect OpenClaw to Verifiedemail: link your Verifiedemail account once in the browser and OpenClaw can call the Verifiedemail API through 9 ready-made tools — no custom code or token handling. ### How do I add Verifiedemail to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Verifiedemail skill from ClawHub, then you click Connect in the dashboard to authorize Verifiedemail. OpenClaw calls the tools from the next message — no config files, and the Verifiedemail key you paste is stored server-side instead of in your environment. ### How long does it take to connect Verifiedemail to OpenClaw? About two minutes. Sign in, click Connect next to Verifiedemail in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Verifiedemail 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 Verifiedemail working from chat. ### OpenClaw installed the Verifiedemail skill but can't call the tools The ClawHub skill teaches OpenClaw about Verifiedemail, but the calls run through the ClawLink plugin and your connected account. Make sure Verifiedemail 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 - [Connect 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. - [Mailchimp tools](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences