# How to connect Upload-Post to OpenClaw (paste one key, 12 tools) > Connect Upload-Post to OpenClaw with ClawLink: paste your Upload-Post key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/upload-post The usual route to Upload-Post 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 Upload-Post setup: install one ClawHub skill, connect Upload-Post in the browser, and OpenClaw can call real Upload-Post 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 Upload-Post. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Upload-Post** — 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 upload-post # connect Upload-Post (browser OAuth) npx -y @useclawlink/cli actions upload-post # list available actions npx -y @useclawlink/cli run upload-post --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 Upload-Post in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Upload-Post API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Upload-Post, 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 Upload-Post is connected in the dashboard, that agent calls the same 12 Upload-Post 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). ## Upload-Post MCP for OpenClaw Looking for a Upload-Post MCP server for OpenClaw? ClawLink connects Upload-Post to OpenClaw and exposes 12 Upload-Post 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 Upload-Post integration](https://claw-link.dev/hermes/upload-post) works the same way. ## What the OpenClaw Upload-Post integration can do 12 Upload-Post tools are ready for OpenClaw once the account is connected. ### All 12 Upload-Post tools for OpenClaw | Tool | What it does | |---|---| | **Get upload status** `upload_post_get_upload_status` | Get the processing status and per-platform results for an asynchronous or scheduled upload | | **List cached post analytics** `upload_post_list_cached_post_analytics` | Return one page of cached per-post analytics for a profile without consuming the live | | **List platform destinations** `upload_post_list_platform_destinations` | List selectable Facebook Pages, LinkedIn organizations, Pinterest boards, or Google Business | | **List profiles** `upload_post_list_profiles` | List Upload-Post profiles and their connected social accounts | | **List scheduled posts** `upload_post_list_scheduled_posts` | Return one page of pending scheduled posts and the job IDs needed to edit or cancel them | | **List upload history** `upload_post_list_upload_history` | Return one page of past and in-progress Upload-Post uploads, including platform post IDs, URLs | | **Create profile** `upload_post_create_profile` | Create an Upload-Post profile for a unique caller-owned username; this does not connect any | | **Update scheduled post** `upload_post_update_scheduled_post` | Change the future publication time, title, or caption of an existing scheduled post | | **Cancel scheduled post** `upload_post_cancel_scheduled_post` | Permanently cancel a scheduled post before publication and delete its staged assets | | **Enqueue post** `upload_post_enqueue_post` | Insert one video, photo carousel, or text post into a profile's external publication queue | | **Publish post** `upload_post_publish_post` | Immediately publish one video, photo carousel, or text post to external connected platforms | | **Schedule post** `upload_post_schedule_post` | Schedule one video, photo carousel, or text post for future external publication to connected | ## Example prompts **Get Upload Status** > Pull the relevant data from Upload-Post, summarize it in plain English, and point out anything that needs attention. **List Cached Post Analytics** > List the relevant items in Upload-Post, group them by priority, and recommend what OpenClaw should do next. **List Platform Destinations** > List the relevant items in Upload-Post, group them by priority, and recommend what OpenClaw should do next. **List Profiles** > List the relevant items in Upload-Post, 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 Upload-Post working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Upload-Post API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Upload-Post 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 Upload-Post. | 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 Upload-Post actions to the runtime in a format your agent can reliably use. | 12 tools for Upload-Post are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Upload-Post 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 Upload-Post in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Upload-Post 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 Upload-Post skill but can't call the tools The ClawHub skill teaches OpenClaw about Upload-Post, but the calls run through the ClawLink plugin and your connected account. Make sure Upload-Post 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 Upload-Post 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 Upload-Post tools Upload-Post 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 Upload-Post 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. ### Upload-Post 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 Upload-Post has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Upload-Post integration? Yes. ClawLink is the fastest way to connect OpenClaw to Upload-Post: link your Upload-Post account once in the browser and OpenClaw can call the Upload-Post API through 12 ready-made tools — no custom code or token handling. ### How do I add Upload-Post to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Upload-Post skill from ClawHub, then you click Connect in the dashboard to authorize Upload-Post. OpenClaw calls the tools from the next message — no config files, and the Upload-Post key you paste is stored server-side instead of in your environment. ### How long does it take to connect Upload-Post to OpenClaw? About two minutes. Sign in, click Connect next to Upload-Post in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Upload-Post 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 Upload-Post working from chat. ### OpenClaw installed the Upload-Post skill but can't call the tools The ClawHub skill teaches OpenClaw about Upload-Post, but the calls run through the ClawLink plugin and your connected account. Make sure Upload-Post 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 - [Connect ActiveCampaign](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. - [Connect Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences