OpenClaw + Wahlu
Use Wahlu’s REST API from your OpenClaw workflow to discover connected accounts, import media and prepare drafts with a clear review point.
Instagram · Facebook · TikTok · YouTube · LinkedIn personal profiles · Threads · X · Bluesky · Telegram · Discord · Tumblr · Pinterest
curl https://api.wahlu.com/v1/context \
-H "Authorization: Bearer $WAHLU_API_KEY"MCP setup depends on your OpenClaw runtime and installed bridge. The REST workflow here works through an HTTP-capable tool; it does not require a Wahlu-specific plugin.
Access depends on the brands and permissions you grant. Your connected accounts determine where each post can go.
Browse your brand’s media through MCP, or import a public image or video through the API. Check that it is ready before attaching it to a post.
Bring the copy from your conversation into Wahlu. Keep platform settings and the intended accounts with the draft.
Check upcoming posts and create schedules with an explicit approval state. A pending-review schedule stays held for review.
Run preflight checks for content, media and account readiness. Read returned blockers and publishing results before deciding what to do next.
Example prompts and the steps to expect. These are illustrations, not recorded conversations.
Example prompt
“Prepare a post from this approved article. Use the matching Wahlu brand, check the media and create a schedule held for review.”
Your workflow supplies the content and calls the documented API. Carry forward the returned brand, media and draft IDs, and stop when a readiness check needs attention.
Example prompt
“Check this draft for publishing problems. Tell me what needs fixing before you schedule anything.”
The preflight check reports readiness without creating a schedule or publishing a post. The agent should explain any blockers and the next action.
Start with one brand and a workflow that prepares content for review.
Create a scoped key in Wahlu under Settings → API Keys. Store it in your workflow’s secret environment, then make a request to the context endpoint.
curl https://api.wahlu.com/v1/context \
-H "Authorization: Bearer $WAHLU_API_KEY"MCP setup depends on your OpenClaw runtime and installed bridge. The REST workflow here works through an HTTP-capable tool; it does not require a Wahlu-specific plugin.
The context response identifies the brands available to your key. Use its links and returned IDs in later requests instead of inventing them.
Keep the API key in your runtime’s secret store. Give each integration its own key so you can revoke it independently.
Check the wording, media and account selection. Agents can change the name or caption of an unused draft. Use the Wahlu app to change draft media and manage recurring queues.
Use pending_review while preparing content. Publication requires the appropriate approval and publishing authority; a successful preparation request is not a published post.
Hosted OAuth, the local stdio package and the supported actions.
Connect an agent and prepare a post with a review step.
Check the current client setup and workspace requirements.
Follow the complete REST workflow with returned IDs and readiness checks.
Connect your social accounts in Wahlu, then give your agent a specific brief.