How to connect WoopSocial to OpenClaw
Connect WoopSocial to OpenClaw with ClawLink: paste your WoopSocial key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine.
WoopSocialAPI KEYMCPWoopSocial provides social media publishing, scheduling, media, project, account, and webhook management through its REST API.. Once connected, OpenClaw can read and act on WoopSocial from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to WoopSocial 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 WoopSocial setup: install one ClawHub skill, connect WoopSocial in the browser, and OpenClaw can call real WoopSocial 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 WoopSocial.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect WoopSocial
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with WoopSocial?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 WoopSocial in the ClawLink dashboard — paste your WoopSocial API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from WoopSocial, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once WoopSocial is connected in the dashboard, that agent calls the same 20 WoopSocial tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
WoopSocial MCP for OpenClaw
Looking for a WoopSocial MCP server for OpenClaw? ClawLink connects WoopSocial to OpenClaw and exposes 20 WoopSocial tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes WoopSocial integration works the same way.
What the OpenClaw WoopSocial integration can do
20 WoopSocial tools are ready for OpenClaw once the account is connected. The 14 below are the ones people reach for most; your agent can call all 20.
14 of 20 WoopSocial tools for OpenClaw
| Tool | What it does |
|---|---|
Get post woop_social_get_post | Get a parent post and its per-social-account delivery records by post ID |
Get social account platform inputs woop_social_get_social_account_platform_inputs | Get dynamic Pinterest board choices or TikTok posting-policy options for a connected social |
List media woop_social_list_media | List one page of WoopSocial media-library items, optionally filtered by project or exact media |
List projects woop_social_list_projects | List all projects accessible to the connected WoopSocial API key |
List social account posts woop_social_list_social_account_posts | List one page of per-account post deliveries, optionally filtered by projects, social accounts |
List social accounts woop_social_list_social_accounts | List connected social accounts available for publishing, optionally within one project |
List webhooks woop_social_list_webhooks | List registered WoopSocial webhook endpoints and their subscribed events |
Validate post woop_social_validate_post | Validate a proposed WoopSocial post without creating it |
Create draft post woop_social_create_draft_post | Save a post as a WoopSocial draft without publishing it externally |
Create project woop_social_create_project | Create a WoopSocial project in the API key's organization |
Register webhook woop_social_register_webhook | Register a public HTTPS endpoint for WoopSocial publishing-success and/or publishing-failure |
Upload media woop_social_upload_media | Upload one image or video of at most 100 MB into a WoopSocial project using the atomic |
Publish post now woop_social_publish_post_now | Publish a post to external social platforms now; external publication is an irreversible action |
Schedule post woop_social_schedule_post | Schedule automatic future publication to external social platforms; that future publication is |
Try it: find the WoopSocial tool you need
Browse the 14 WoopSocial tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from WoopSocial, summarize it in plain English, and point out anything that needs attention.
List the relevant items in WoopSocial, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in WoopSocial, group them by priority, and recommend what OpenClaw should do next.
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 WoopSocial working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the WoopSocial API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected WoopSocial 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 WoopSocial. | 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 WoopSocial actions to the runtime in a format your agent can reliably use. | 20 tools for WoopSocial are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes WoopSocial 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 WoopSocial in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the WoopSocial key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the WoopSocial skill but can't call the tools
The ClawHub skill teaches OpenClaw about WoopSocial, but the calls run through the ClawLink plugin and your connected account. Make sure WoopSocial 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 WoopSocial 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 WoopSocial tools
WoopSocial 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 WoopSocial 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.
WoopSocial 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 WoopSocial has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw WoopSocial integration?
Yes. ClawLink is the fastest way to connect OpenClaw to WoopSocial: link your WoopSocial account once in the browser and OpenClaw can call the WoopSocial API through 20 ready-made tools — no custom code or token handling.
How do I add WoopSocial to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink WoopSocial skill from ClawHub, then you click Connect in the dashboard to authorize WoopSocial. OpenClaw calls the tools from the next message — no config files, and the WoopSocial key you paste is stored server-side instead of in your environment.
How long does it take to connect WoopSocial to OpenClaw?
About two minutes. Sign in, click Connect next to WoopSocial in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring WoopSocial 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 WoopSocial working from chat.
OpenClaw installed the WoopSocial skill but can't call the tools
The ClawHub skill teaches OpenClaw about WoopSocial, but the calls run through the ClawLink plugin and your connected account. Make sure WoopSocial 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.
