We are finishing the Threads integration for OpenClaw. Check back soon for platform-specific workflows, examples, and setup guides.
10:24●●●●100%
‹
OpenClaw
bot
WhatsApp · Telegram · Slack
TODAY
Schedule my launch post on Facebook, Instagram, and Threads with the cover image for tomorrow at 9am 10:22 AM
Queued on your Majika calendar:
• Facebook — 9:00 AM
• Instagram — 9:00 AM
• Threads — 9:00 AM
Post ref: oq-7f3a · review before publish
10:23 AM
📎
Message
🎤
Your messaging apps
Text from TelegramWhatsAppor Slack
Send a scheduling request to OpenClaw like any other message. The openquok-core skill runs on your host, finds connected channels, attaches media, and queues drafts — you approve on the calendar before anything publishes.
Built for Meta Threads with OpenClaw
Who schedules Threads with OpenClaw?
Creators & founders
Stay consistent on Threads without daily manual posting. Queue text, images, and reply chains on the calendar while you focus on building. Message OpenClaw to draft Threads posts from chat — you approve before publish.
Social managers
Batch a week of Threads in one sitting, review drafts before they publish, and track views and engagement alongside your other channels. OpenClaw queues Threads drafts at volume — your team approves before publish.
Developers & agents
Pipe Threads drafts from your backend via the public API or CLI — including follow-up replies under providerSettings — while you keep approval control in the dashboard. Run OpenClaw per client workspace so Threads drafts stay isolated.
How it works
Five steps,to OpenClaw + Majika
Connect Once
login from your phonepick your workspacechat anywhere securely
Choose a workspace, connect with OAuth2 — approve in your browser, and credentials stay on the host. Message OpenClaw from Telegram, WhatsApp, or Slack to draft and schedule without opening another app.
I'm still waiting for authorization. Open the link, sign in, pick your workspace, then tap Authorize: openquok.com/cli/device/verify?code=DYKK-KRFV5:21 PM
check if I am logged in 5:23 PM
You're all set! Authentication was successful, and I've found your Threads integration for
@rati.mon 5:23 PM
📎
Message
🎤
Create Post
Connected channels
Editing a Specific Network Back to global
57 / 500
Follow-up comments
Reply
39/500
Delay
09:00 + 300s≈ 09:05:00
Majika Settings
Add a thread finisher
14/500
Delayed reply
Same account — schedules extra reply (internal plug).
Reply message
0/500
Post Preview
MajikaMajika
Jun 12, 9:00 AM
Attach media and queue one follow-up reply after publish.
1
Scheduled thread replies
Majika
After 5 min
Each reply runs after your chosen delay
Majika
Thread finisher
That's a wrap — thanks for reading.
Media & replies
Attach image or videoschedule follow-up repliesin one place
Create post within Threads's 500-character limit, attach a single image, carousel or video, and queue replies with delays before the thread goes live.
See what resonates on Threadstrack views and engagementand iterate
Track views, likes, replies, reposts, and quotes from connected Threads profiles inside Majika analytics — so you can schedule more of what already works.
Schedule my launch post on Facebook, Instagram, and Threads with the cover image for tomorrow at 9am 10:22 AM
Queued on your Majika calendar:
• Facebook — 9:00 AM
• Instagram — 9:00 AM
• Threads — 9:00 AM
Post ref: oq-7f3a · review before publish
10:23 AM
📎
Message
🎤
Scale what works
when a format hits,scale by adding workspaces and parallel sessions
Spot a winner in analytics, then clone more dedicated workspaces for the next client or brand while OpenClaw queues the next wave in parallel — credentials, channels, and agent context stay isolated as you scale.
What OpenClaw is, how to install openquok-core, scheduling Threads posts, human approval, and how agents draft from chat.
OpenClaw is the open-source personal AI agent. It runs locally or on your own host, connects to chat apps you already use, and takes real actions on your behalf — including drafting and scheduling social media through Majika.
From your OpenClaw workspace directory, run npx skills add on the agent package root with --skill openquok-core (add -y on headless hosts), or after ClawHub publish run clawhub install openquok-core. Install the global CLI with npm install -g @openquok/auto-cli, set OPENQUOK_API_KEY from Account → Settings → Developers → Access or run openquok auth:login --json, and OpenClaw discovers the skill automatically. See the OpenClaw agent guide in Dev Docs for the exact commands.
OpenClaw can draft and schedule Threads posts, upload images and video, apply per-platform settings, and pull platform and post analytics for your connected Threads account. The openquok-core skill documents integrations:list, posts:create, posts:status, analytics:platform, upload, and more — every command returns structured JSON for the agent to parse.
Connect your Threads account in the Majika web app, install openquok-core on OpenClaw, and message your assistant to schedule. OpenClaw uses integration UUIDs from openquok integrations:list to target your Threads account. Every post lands as a draft or scheduled item until you approve on the calendar or kanban.
Posts created through the CLI land in your Majika workspace as drafts or scheduled items — nothing goes live on autopilot. You review on the calendar or kanban, move posts through draft and review, and approve what should publish. OpenClaw handles volume; you handle quality.
Yes. Majika is CLI-first — any agent that can run shell commands can use openquok, including Claude Code, ChatGPT, and custom automation. This page focuses on OpenClaw plus the openquok-core skill; pair it with other OpenClaw skills (Bloom, RevenueCat, or your own) for richer workflows.
MCP clients like Codex, Claude Code, and Cursor fit focused editor and terminal sessions. OpenClaw fits always-on scheduling from Telegram, WhatsApp, or Slack — persistent memory, parallel sessions across channels, and one assistant that can run openquok-core beside your other skills. Choose OpenClaw when messaging and scale matter; choose MCP when Majika should live inside a single coding workflow. Many teams use both.
Yes. Mount a persistent workspace volume, set OPENCLAW_WORKSPACE_DIR, install openquok-core and the global CLI in the container shell, then authenticate. On headless hosts prefer OPENQUOK_API_KEY or openquok auth:login --json so the user opens verification_uri_complete on another device. Start a new chat session after upgrades so the agent reloads instructions.
Yes. Create an Majika account and start a 7-day free trial, connect your channels, install openquok-core on OpenClaw, and begin scheduling from chat.
Read the OpenClaw setup guide
Step-by-step instructions for connecting Majika to OpenClaw — install commands, auth patterns, and configuration snippets.