# How to connect Elastic Email to OpenClaw (paste one key, 91 tools) > Connect Elastic Email to OpenClaw with ClawLink: paste your Elastic Email key once and 91 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/elastic-email The usual route to Elastic Email 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 Elastic Email setup: install one ClawHub skill, connect Elastic Email in the browser, and OpenClaw can call real Elastic Email 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 Elastic Email. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Elastic Email** — 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 elastic-email # connect Elastic Email (browser OAuth) npx -y @useclawlink/cli actions elastic-email # list available actions npx -y @useclawlink/cli run elastic-email --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 Elastic Email in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Elastic Email API key once. Verify the connection by asking OpenClaw: > Use Elastic Email to check domain restricted 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 Elastic Email is connected in the dashboard, that agent calls the same 91 Elastic Email 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). ## Elastic Email MCP for OpenClaw Looking for a Elastic Email MCP server for OpenClaw? ClawLink connects Elastic Email to OpenClaw and exposes 91 Elastic Email 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 Elastic Email integration](https://claw-link.dev/hermes/elastic-email) works the same way. ## What the OpenClaw Elastic Email integration can do 91 Elastic Email 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 91. ### 30 of 91 Elastic Email tools for OpenClaw | Tool | What it does | |---|---| | **Check domain restricted** `elastic_email_check_domain_restricted` | Check whether Elastic Email restricts a domain or identifies it as a free-provider domain | | **Download file** `elastic_email_download_file` | Download a stored Elastic Email file by its exact name | | **Download verification file results** `elastic_email_download_verification_file_results` | Download the ZIP result archive for a completed verification file job | | **Get campaign** `elastic_email_get_campaign` | Return one Elastic Email campaign by its exact name | | **Get contact** `elastic_email_get_contact` | Return one Elastic Email contact by email address | | **Get contact export status** `elastic_email_get_contact_export_status` | Get the current status of an asynchronous contact export job | | **Get contact list** `elastic_email_get_contact_list` | Return one Elastic Email contact list by its exact name | | **Get credential metadata** `elastic_email_get_credential_metadata` | Get one Elastic Email API-key or SMTP credential's audit metadata without returning its secret | | **Get domain** `elastic_email_get_domain` | Return detailed DNS and certificate state for one Elastic Email domain | | **Get email job status** `elastic_email_get_email_job_status` | Return delivery status and optional recipient-level details for an Elastic Email transaction | | **Get email preview** `elastic_email_get_email_preview` | Return the rendered preview, attachment metadata, and delivery status for an Elastic Email | | **Get email verification** `elastic_email_get_email_verification` | Return the saved Elastic Email verification result for one email address | | **Get event export status** `elastic_email_get_event_export_status` | Get the current status of an asynchronous global or channel event export | | **Get file info** `elastic_email_get_file_info` | Return metadata for a stored Elastic Email file without downloading it | | **Get inbound route** `elastic_email_get_inbound_route` | Return one Elastic Email inbound route by its public ID | | **Get segment** `elastic_email_get_segment` | Return one Elastic Email dynamic contact segment by its exact name | | **Get statistics** `elastic_email_get_statistics` | Return aggregate Elastic Email delivery statistics for a time interval | | **Get statistics breakdown** `elastic_email_get_statistics_breakdown` | Return one Elastic Email campaign or channel delivery summary by exact name | | **Get subaccount** `elastic_email_get_subaccount` | Return one managed Elastic Email subaccount by its login email | | **Get suppression** `elastic_email_get_suppression` | Return suppression details for one Elastic Email address | | **Get template** `elastic_email_get_template` | Return one Elastic Email template by its exact name | | **Get verification file results** `elastic_email_get_verification_file_results` | Return one page of detailed results and metadata for a verification file | | **Get webhook** `elastic_email_get_webhook` | Return one Elastic Email webhook subscription by its public ID | | **List campaigns** `elastic_email_list_campaigns` | Find campaigns by optional name fragment and return one page | | **List contact list members** `elastic_email_list_contact_list_members` | Return one page of contacts in a named Elastic Email contact list | | **List contact lists** `elastic_email_list_contact_lists` | Return one page of contact lists from the connected Elastic Email account | | **List contacts** `elastic_email_list_contacts` | Return one page of contacts from the connected Elastic Email account | | **List credential metadata** `elastic_email_list_credential_metadata` | List API-key or SMTP credential metadata without returning secret tokens | | **List domains** `elastic_email_list_domains` | Return all sending and tracking domains configured for the account | | **List email verifications** `elastic_email_list_email_verifications` | Return one page of individual email verification results | ## Example prompts **Check Domain Restricted** > Use Elastic Email to check domain restricted and walk me through the result in plain English. **Download File** > Use Elastic Email to download file and walk me through the result in plain English. **Download Verification File Results** > Use Elastic Email to download verification file results and walk me through the result in plain English. **Get Campaign** > Pull the relevant data from Elastic Email, 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 Elastic Email working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Elastic Email API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Elastic Email 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 Elastic Email. | 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 Elastic Email actions to the runtime in a format your agent can reliably use. | 91 tools for Elastic Email are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Elastic Email 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 Elastic Email in the browser, and the 91 tools above work from chat. There is no SDK and no config file, and the Elastic Email 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 Elastic Email skill but can't call the tools The ClawHub skill teaches OpenClaw about Elastic Email, but the calls run through the ClawLink plugin and your connected account. Make sure Elastic Email 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 Elastic Email 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 Elastic Email tools Elastic Email 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 Elastic Email 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. ### Elastic Email 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 Elastic Email has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Elastic Email integration? Yes. ClawLink is the fastest way to connect OpenClaw to Elastic Email: link your Elastic Email account once in the browser and OpenClaw can call the Elastic Email API through 91 ready-made tools — no custom code or token handling. ### How do I add Elastic Email to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Elastic Email skill from ClawHub, then you click Connect in the dashboard to authorize Elastic Email. OpenClaw calls the tools from the next message — no config files, and the Elastic Email key you paste is stored server-side instead of in your environment. ### How long does it take to connect Elastic Email to OpenClaw? About two minutes. Sign in, click Connect next to Elastic Email in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Elastic Email 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 Elastic Email working from chat. ### OpenClaw installed the Elastic Email skill but can't call the tools The ClawHub skill teaches OpenClaw about Elastic Email, but the calls run through the ClawLink plugin and your connected account. Make sure Elastic Email 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 - [ActiveCampaign tools](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email tools](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