# How to connect BulkPublish to OpenClaw (paste one key, 10 tools) > Connect BulkPublish to OpenClaw with ClawLink: paste your BulkPublish key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/bulkpublish The usual route to BulkPublish 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 BulkPublish setup: install one ClawHub skill, connect BulkPublish in the browser, and OpenClaw can call real BulkPublish 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 BulkPublish. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect BulkPublish** — 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 bulkpublish # connect BulkPublish (browser OAuth) npx -y @useclawlink/cli actions bulkpublish # list available actions npx -y @useclawlink/cli run bulkpublish --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 BulkPublish in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your BulkPublish API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from BulkPublish, 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 BulkPublish is connected in the dashboard, that agent calls the same 10 BulkPublish 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). ## BulkPublish MCP for OpenClaw Looking for a BulkPublish MCP server for OpenClaw? ClawLink connects BulkPublish to OpenClaw and exposes 10 BulkPublish 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 BulkPublish integration](https://claw-link.dev/hermes/bulkpublish) works the same way. ## What the OpenClaw BulkPublish integration can do 10 BulkPublish tools are ready for OpenClaw once the account is connected. ### All 10 BulkPublish tools for OpenClaw | Tool | What it does | |---|---| | **Get analytics summary** `bulkpublish_get_analytics_summary` | Summarize post counts by status, platform, and day for a required date range of up to 30 days | | **Get API request usage** `bulkpublish_get_api_request_usage` | Return today's organization-wide API request count, daily limit, plan, and per-key breakdown | | **Get plan usage** `bulkpublish_get_plan_usage` | Return the connected organization's plan, feature limits, and current resource usage | | **Get platform availability** `bulkpublish_get_platform_availability` | Return current connection and publishing availability for every supported platform and platform | | **List activity** `bulkpublish_list_activity` | Return one page of organization audit activity, optionally filtered by action or resource type | | **List channels** `bulkpublish_list_channels` | Return active connected social channels by default, or inactive channels when active is false | | **List labels** `bulkpublish_list_labels` | Return post or media labels available in the connected organization | | **List media** `bulkpublish_list_media` | Search uploaded media by filename or labels and return one page of files | | **List notifications** `bulkpublish_list_notifications` | Return one page of organization notifications, optionally restricted to unread items | | **List posts** `bulkpublish_list_posts` | Search and filter the connected organization's posts, returning one page and a cursor when more | ## Example prompts **Get Analytics Summary** > Pull the relevant data from BulkPublish, summarize it in plain English, and point out anything that needs attention. **Get Api Request Usage** > Pull the relevant data from BulkPublish, summarize it in plain English, and point out anything that needs attention. **Get Plan Usage** > Pull the relevant data from BulkPublish, summarize it in plain English, and point out anything that needs attention. **Get Platform Availability** > Pull the relevant data from BulkPublish, 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 BulkPublish working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the BulkPublish API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected BulkPublish 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 BulkPublish. | 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 BulkPublish actions to the runtime in a format your agent can reliably use. | 10 tools for BulkPublish are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes BulkPublish 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 BulkPublish in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the BulkPublish 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 BulkPublish skill but can't call the tools The ClawHub skill teaches OpenClaw about BulkPublish, but the calls run through the ClawLink plugin and your connected account. Make sure BulkPublish 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 BulkPublish 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 BulkPublish tools BulkPublish 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 BulkPublish 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. ### BulkPublish 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 BulkPublish has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw BulkPublish integration? Yes. ClawLink is the fastest way to connect OpenClaw to BulkPublish: link your BulkPublish account once in the browser and OpenClaw can call the BulkPublish API through 10 ready-made tools — no custom code or token handling. ### How do I add BulkPublish to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink BulkPublish skill from ClawHub, then you click Connect in the dashboard to authorize BulkPublish. OpenClaw calls the tools from the next message — no config files, and the BulkPublish key you paste is stored server-side instead of in your environment. ### How long does it take to connect BulkPublish to OpenClaw? About two minutes. Sign in, click Connect next to BulkPublish in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring BulkPublish 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 BulkPublish working from chat. ### OpenClaw installed the BulkPublish skill but can't call the tools The ClawHub skill teaches OpenClaw about BulkPublish, but the calls run through the ClawLink plugin and your connected account. Make sure BulkPublish 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 - [OpenClaw Benchmark Email integration](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