OpenClaw + PostOnce

Publish social posts with OpenClaw

Connect your OpenClaw agent to PostOnce to publish updates, check delivery, and manage automatic crossposting from your connected accounts.

Connect OpenClaw

Requires a PostOnce account, API access, and your own API key.

See setup steps

Set up your connection

Connect OpenClaw to PostOnce

Use your own PostOnce API key.

1
Prepare your PostOnce account
You need API access on your plan and at least one connected social account. Create a dedicated key with accounts:read for your first check; add posts, media, or workflow scopes only for the actions you want.
Create an API key Connect social accounts Check plan access
2
Connect through OpenClaw’s native MCP registry
Use OpenClaw 2026.9.3 with Node 24.16–24.x or 26.1+. Supply POSTONCE_API_KEY privately to the Gateway or runtime process. If a PostOnce server is already configured, inspect it before making changes; otherwise run this command from your intended agent workspace.
Terminal · OpenClaw CLI
```
openclaw mcp add postonce --url https://postonce.to/mcp --transport streamable-http --header 'Authorization=Bearer ${POSTONCE_API_KEY}' --no-probe
```
Follow the client-specific instructions above. Keep your API key out of agent conversations and public files.
Keep the single quotes: they store the environment variable reference, not your key. Restart the runtime after changing its private environment. A remote Gateway needs the key on that machine; setting it in your local terminal does not configure another host.
Use an agent profile that permits MCP tools, such as coding or messaging. A minimal profile or explicit bundle-mcp denial hides these tools. Keep your existing approval and tool policies; this setup does not override them.
3
Check the connection
Run the probe to check that OpenClaw can discover PostOnce’s tools. Then start a new agent session and ask for your connected accounts. A saved configuration alone does not confirm authentication.
Terminal · check tool discovery
```
openclaw mcp probe postonce --json
```
Try this prompt
Show my connected social accounts.
Expect account names, platforms, and IDs from list_active_accounts. Choose actual accounts before asking the agent to publish.

Optional · after connecting

Add the PostOnce workflow skill

Give OpenClaw reusable guidance for choosing accounts, preparing media, publishing, and checking delivery. Installing the skill adds instructions; it does not authenticate or grant access.

Download and extract the ZIP into a dedicated directory. Read its SKILL.md and README before installing. Keep an existing PostOnce skill’s custom instructions; do not force an overwrite.
From your intended agent workspace, replace the example path below with the extracted postonce directory. The installer takes the directory, not the ZIP.
Terminal · install the extracted skill
```
openclaw skills install /absolute/path/to/extracted/postonce
```
Start a new OpenClaw session and ask it to use the PostOnce skill to show your connected accounts. A remote runtime needs its own skill installation and connection.

Download skill · v0.1.0 OpenClaw skill documentation SHA-256 checksums

Read the connection documentation

From connection to first result

Start with one useful action

Find your accounts

Try this prompt

Show my connected social accounts.

Use the returned names and IDs to choose your targets. If nothing appears, connect an account in the dashboard.

Publish an update

Try this prompt

Help me publish a product update. First show my connected accounts, then ask me to choose the destinations and confirm the exact text before publishing.

After creation, ask for the post ID and each destination’s delivery status. A queued post is still waiting to publish.

Set up crossposting

Try this prompt

Show my connected accounts and the available crossposting options. Help me choose a supported source and destinations, then confirm the workflow before creating it.

A created workflow applies to future matching source posts. Inspect the workflow in PostOnce before relying on it.

Review posts in PostOnce Review crossposting workflows

Know what your agent can access

Connected accounts and scoped actions

PostOnce uses your API key’s scopes and existing account permissions. Your available destinations come from your connected accounts; media and text requirements still vary by platform.

Media needs a supported upload path

The hosted server cannot read a file path on your computer or assume access to a chat attachment. For a first media post, use a supported publicly accessible media URL and have the agent validate the selected platform’s requirements before publishing.

Media post example

Help me publish an image from a public media URL. Ask me for the URL, text, and connected destination accounts; check the platform requirements and confirm the post before creating it.

Questions before connecting

Do I need a particular PostOnce plan?

You need a plan with Public API access. Your API keys tab checks your account’s actual entitlement and shows an upgrade option when required. Connecting a client does not change your plan.

What if my agent shows no social accounts?

Connect or reconnect a social account in PostOnce, then ask the agent to list active accounts again. The API key must belong to the same PostOnce account and include accounts:read.

How do I check a failed or queued post?

Ask the agent to get the post using its returned ID and inspect each target’s status and error. Review the post in the dashboard. Check the existing result before creating another post to avoid duplicates.

How do I disconnect or replace the key?

Revoke the dedicated API key in Preferences → API keys and remove the server from your client. To reconnect, create a new key with the scopes you need and replace the old key in the client’s private configuration.