# How to connect Bigmailer to OpenClaw (paste one key, 57 tools) > Connect Bigmailer to OpenClaw with ClawLink: paste your Bigmailer key once and 57 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/bigmailer The usual route to Bigmailer 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 Bigmailer setup: install one ClawHub skill, connect Bigmailer in the browser, and OpenClaw can call real Bigmailer 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 Bigmailer. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Bigmailer** — 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 bigmailer # connect Bigmailer (browser OAuth) npx -y @useclawlink/cli actions bigmailer # list available actions npx -y @useclawlink/cli run bigmailer --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 Bigmailer in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bigmailer API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Bigmailer, 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 Bigmailer is connected in the dashboard, that agent calls the same 57 Bigmailer 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). ## Bigmailer MCP for OpenClaw Looking for a Bigmailer MCP server for OpenClaw? ClawLink connects Bigmailer to OpenClaw and exposes 57 Bigmailer 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 Bigmailer integration](https://claw-link.dev/hermes/bigmailer) works the same way. ## What the OpenClaw Bigmailer integration can do 57 Bigmailer 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 57. ### 30 of 57 Bigmailer tools for OpenClaw | Tool | What it does | |---|---| | **Get brand** `bigmailer_get_brand` | Retrieve detailed information about a specific brand by its ID | | **Get brand property** `bigmailer_get_brand_property` | Retrieve a specific brand property by its ID for a given brand | | **Get bulk campaign** `bigmailer_get_bulk_campaign` | Retrieve detailed information about a specific bulk campaign in BigMailer | | **Get contact** `bigmailer_get_contact` | Retrieve detailed information about a specific contact from BigMailer | | **Get contact batch** `bigmailer_get_contact_batch` | Retrieve the status and results of a contact batch upload in BigMailer | | **Get field** `bigmailer_get_field` | Retrieve a custom field from a BigMailer brand | | **Get list** `bigmailer_get_list` | Retrieve details of a specific list within a brand | | **Get segment** `bigmailer_get_segment` | Retrieve a specific segment from BigMailer by brand ID and segment ID | | **Get suppression list** `bigmailer_get_suppression_list` | Retrieve details of a specific suppression list for a brand in BigMailer | | **Get template** `bigmailer_get_template` | Retrieve detailed information about a specific template by its ID | | **Get transactional campaign** `bigmailer_get_transactional_campaign` | Retrieve detailed information about a specific transactional campaign in BigMailer | | **Get user** `bigmailer_get_user` | Retrieve detailed information about a specific user by their ID | | **Get user info** `bigmailer_get_user_info` | Retrieves information about the authenticated user in BigMailer using the GET /me endpoint | | **List all brands** `bigmailer_list_all_brands` | Retrieves a list of all brands associated with the authenticated BigMailer account | | **List brand properties** `bigmailer_list_brand_properties` | Retrieve a list of brand properties for a specific brand in BigMailer | | **List bulk campaigns** `bigmailer_list_bulk_campaigns` | List bulk campaigns for a specified brand in BigMailer | | **List connections** `bigmailer_list_connections` | List all connections in your BigMailer account | | **List contacts** `bigmailer_list_contacts` | List contacts for a brand in BigMailer | | **List fields** `bigmailer_list_fields` | List custom fields for a brand in BigMailer | | **List lists** `bigmailer_list_lists` | Retrieve all contact lists for a specified brand in BigMailer | | **List message types** `bigmailer_list_message_types` | List message types for a specific brand in BigMailer | | **List segments** `bigmailer_list_segments` | List segments for a brand in BigMailer | | **List senders** `bigmailer_list_senders` | List all senders configured for a specific brand in BigMailer | | **List suppression lists** `bigmailer_list_suppression_lists` | List suppression lists for a specific brand | | **List templates** `bigmailer_list_templates` | List templates for a brand in BigMailer | | **List transactional campaigns** `bigmailer_list_transactional_campaigns` | List transactional campaigns for a specified brand in BigMailer | | **List users** `bigmailer_list_users` | List all users in your BigMailer account | | **Create brand** `bigmailer_create_brand` | Create a new brand in BigMailer | | **Create brand property** `bigmailer_create_brand_property` | Create a brand property in BigMailer | | **Create bulk campaign** `bigmailer_create_bulk_campaign` | Create a bulk email campaign in BigMailer | ## Example prompts **Get Brand** > Pull the relevant data from Bigmailer, summarize it in plain English, and point out anything that needs attention. **Get Brand Property** > Pull the relevant data from Bigmailer, summarize it in plain English, and point out anything that needs attention. **Get Bulk Campaign** > Pull the relevant data from Bigmailer, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Bigmailer, 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 Bigmailer working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Bigmailer API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bigmailer 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 Bigmailer. | 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 Bigmailer actions to the runtime in a format your agent can reliably use. | 57 tools for Bigmailer are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Bigmailer 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 Bigmailer in the browser, and the 57 tools above work from chat. There is no SDK and no config file, and the Bigmailer 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 Bigmailer skill but can't call the tools The ClawHub skill teaches OpenClaw about Bigmailer, but the calls run through the ClawLink plugin and your connected account. Make sure Bigmailer 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 Bigmailer 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 Bigmailer tools Bigmailer 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 Bigmailer 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. ### Bigmailer 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 Bigmailer has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Bigmailer integration? Yes. ClawLink is the fastest way to connect OpenClaw to Bigmailer: link your Bigmailer account once in the browser and OpenClaw can call the Bigmailer API through 57 ready-made tools — no custom code or token handling. ### How do I add Bigmailer to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bigmailer skill from ClawHub, then you click Connect in the dashboard to authorize Bigmailer. OpenClaw calls the tools from the next message — no config files, and the Bigmailer key you paste is stored server-side instead of in your environment. ### How long does it take to connect Bigmailer to OpenClaw? About two minutes. Sign in, click Connect next to Bigmailer in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Bigmailer 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 Bigmailer working from chat. ### OpenClaw installed the Bigmailer skill but can't call the tools The ClawHub skill teaches OpenClaw about Bigmailer, but the calls run through the ClawLink plugin and your connected account. Make sure Bigmailer 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