Skip to content
BuzzTake
MenuClose

OpenClaw by OpenClaw Foundation

OpenClaw answers your DMs from Telegram

Text OpenClaw in the chat app you already use. It reads the new messages on Instagram, X and LinkedIn through BuzzTake, drafts the answers, and sends the ones you agree to.

Connects through
Remote MCP, OAuth or a key header
Config
~/.openclaw/openclaw.json
Transport
Set streamable-http, the default is SSE
Answers in
WhatsApp, Telegram, Slack and more
OpenClaw, sample run. A Telegram chat with OpenClaw at 8:10. The user asks what is new on Instagram. OpenClaw lists three new conversations, drafts two answers about sizes and asks to send them. The user presses Send, and two Instagram replies change from draft to sent.

What OpenClaw can do in your social accounts

OpenClaw lives in about thirty chat channels, among them WhatsApp, Telegram, Discord, Slack, Signal, iMessage and LINE. Its gateway runs on your computer or on a server and holds the MCP sessions.

With BuzzTake added to the gateway, a message such as "anything new on Instagram?" becomes list_conversations and read_conversation calls, and "send the two answers" becomes two send_message calls in the right threads.

OpenClaw's scheduled jobs post into a chat too. A job at 8:00 can read the night's messages and mentions and send you one summary in Telegram, with the drafts ready to approve.

It works on Instagram, X, LinkedIn, Facebook and Telegram, and on every other platform BuzzTake connects. Each action is one tool, named as in the actions reference.

Jobs for OpenClaw

Say it in plain words. These are prompts that work, and the calls they make.

  1. Answer the night's Instagram messages

    In the morning you ask what came in. OpenClaw reads the new conversations, groups them and drafts an answer for each, and sends the ones you confirm.

    What came in on Instagram overnight? Draft answers, and send the ones I say yes to.

    1 × list_conversations, 3 × read_conversation, 2 × send_message36 credits ($0.36)

  2. A summary at 8:00 in Telegram

    A scheduled job reads your notifications on three platforms and sends you one message with what needs an answer.

    Every weekday at 8:00, read my X, LinkedIn and Bluesky notifications with BuzzTake and send me what needs an answer.

    3 × read_notifications12 credits ($0.12)

  3. Post a photo from your phone

    Send a photo and a line of text to OpenClaw, and it uploads the photo and posts it to Instagram and Facebook.

    Post this photo to Instagram and our Facebook page with: Fresh bread from 7:00 tomorrow.

    2 × post20 credits ($0.20)

  4. Answer a comment while you travel

    OpenClaw reads the replies under your newest LinkedIn post and answers the question you point at.

    Read the replies under our newest LinkedIn post. Answer Priya's question about the API with a link to the docs.

    1 × read_post, 1 × reply12 credits ($0.12)

Set up OpenClaw

Do this on the machine that runs the OpenClaw gateway. It can be your computer or a server: BuzzTake is reached over the internet.

  1. Add the server

    Add BuzzTake under mcp.servers in ~/.openclaw/openclaw.json. Set transport yourself: without it OpenClaw uses SSE, and BuzzTake serves streamable HTTP. The gateway picks up the edit by itself.

    ~/.openclaw/openclaw.json
    {
      "mcp": {
        "servers": {
          "buzztake": {
            "url": "https://mcp.buzztake.com/mcp",
            "transport": "streamable-http",
            "auth": "oauth"
          }
        }
      }
    }
  2. Sign in

    openclaw mcp login does not run while the local gateway runs, so stop it first. Or use the Control UI: Settings, MCP, Sign in. On a host without a browser, run the --code command that the login prints.

    Terminal
    openclaw gateway stop
    openclaw mcp login buzztake
    openclaw mcp doctor buzztake --probe
    openclaw gateway start
  3. Text it

    In your chat app, ask for something that changes nothing.

    Message
    Which BuzzTake accounts do I have?

Ways to connect OpenClaw

The routes that reach BuzzTake from OpenClaw, and how well each one fits.

Remote MCP, OAuth sign-inBest fit

OpenClaw registers itself as a public client and signs in with PKCE. BuzzTake accepts both.

Remote MCP, API keyWorks

Put BUZZTAKE_API_KEY=btk1_... in ~/.openclaw/.env and send it as a header. Leave out auth: while auth is oauth, OpenClaw ignores a fixed Authorization header.

~/.openclaw/openclaw.json
{
  "mcp": {
    "servers": {
      "buzztake": {
        "url": "https://mcp.buzztake.com/mcp",
        "transport": "streamable-http",
        "headers": {
          "Authorization": "Bearer ${BUZZTAKE_API_KEY}"
        }
      }
    }
  }
}
REST APIWorks

OpenClaw's exec tool can run curl. In a Docker sandbox, the network is off by default, so MCP is the simpler route.

POST /v1/accounts/{id}/actions
curl https://api.buzztake.com/v1/accounts/$ACCOUNT_ID/actions \
  -H "Authorization: Bearer $BUZZTAKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type": "post", "text": "Version 2.4 is out.", "wait": 60}'

What it costs

BuzzTake charges in prepaid credits for the actions it runs. One credit is one US cent.

Credits for each job on this page
JobCreditsUSD
Answer the night's Instagram messages36$0.36
A summary at 8:00 in Telegram12$0.12
Post a photo from your phone20$0.20
Answer a comment while you travel12$0.12

A post, a quote or a message is 10 credits, a reply 8, a like or a follow 3, and a read or a search 4. A planned post costs nothing until it goes out. Reads are charged when they succeed, and a write that fails before the page changes is refunded.

OpenClaw's model use is billed by the model provider you set up, not by BuzzTake. Every price is on the pricing page, and the rules are in Credits.

Approvals and safety

A person can approve before anything goes out, and every action is recorded.

Ask OpenClaw to show each draft and wait for your yes before it sends. For a hard stop, give it a BuzzTake key without content_publish: it can then read and plan drafts, and every post waits for a reviewer in BuzzTake.

OpenClaw's exec approvals ask in chat with /approve <id> allow-once, allow-always or deny when tools.exec.mode is set to ask. They cover shell commands, which matters only if you use the curl route.

  • Ask for drafts when a person must check first. create_content puts the post on the calendar, submit_for_review sends it to a reviewer, and it goes out only after the approval.
  • Give the agent an API key without the content_publish permission. It can then plan drafts and send them for review, and it cannot post by itself.
  • BuzzTake records every action: who asked, through which key, on which account, what the page returned and what it cost.
  • A sign-in step that BuzzTake cannot finish, such as a 2FA code, becomes a challenge. The agent asks you for the code, or gives you a link to a live browser where you answer it.
  • Only an owner or an administrator can allow an OAuth client. Disconnect it under Developers in the app, and its token stops working.

More in Approvals and Reports and audit.

Limits

  • A scheduled job made from the command line needs --to with the chat id to deliver to, and uses the gateway host's time zone unless you pass --tz.
  • openclaw mcp reload reloads the command line process only. The gateway reloads openclaw.json by itself.
  • An action tool waits up to 120 seconds for its result. A longer action comes back with its id, and get_action follows it to the end.
  • The MCP server runs up to 8 requests at a time for one key or sign-in. Above that it answers 429 with Retry-After, and the client tries again.
  • One organization connects up to 200 accounts.
  • The platforms set their own pace. When one asks an account to slow down, the action ends with rate_limited, and a write that failed before the page changed is refunded.

Troubleshooting

Every error code and its fix is in Errors and challenges.

openclaw mcp login refuses to run
The local gateway is running. Stop it with openclaw gateway stop, sign in, and start it again, or sign in from the Control UI.
The server connects but no tools arrive
The entry has no transport, so OpenClaw speaks SSE. Set transport to streamable-http.
The client says the server refused the token (401)
The sign-in expired or was revoked, or the API key is wrong. Sign in again from the client, or make a new key under Developers.
An action stops at needs_input
The platform asked for a code. Give the code to the agent so it calls answer_challenge, or open the challenge's sign_in_url and answer in the live browser.
The answer is insufficient_credits
The balance is lower than the price, and nothing was queued. A post needs 10 credits. Top up, then ask again.
The answer is unsupported
The platform has no such action. The error lists the actions it has, and the generic browser action can do the rest step by step.
An account shows signed_out
Its session ended and no stored password could sign it in again. Ask the agent for a sign-in link with get_sign_in_link and open it, or reconnect the account in the app.

OpenClaw questions

Can OpenClaw answer my Instagram DMs?
Yes. With BuzzTake on the gateway, OpenClaw reads your Instagram conversations and sends replies through your own account. Each message sent is 10 credits.
Does OpenClaw need to run on my computer?
No. The gateway can run on your computer or on a server. BuzzTake runs in the cloud, so the gateway reaches it from anywhere.
Will OpenClaw send messages without asking?
Tell it to show drafts and wait for your answer. To make that a rule, use a BuzzTake key without the content_publish permission, so posts need a reviewer's approval.
Which chat apps can I use?
Any OpenClaw channel, such as WhatsApp, Telegram, Discord, Slack, Signal, iMessage or LINE. BuzzTake does not depend on the channel.

All AI agents, the MCP server docs, the quickstart, and the platforms: Instagram X LinkedIn Facebook Telegram

OpenClaw is a trademark of OpenClaw Foundation. Platform names belong to their owners. BuzzTake is not affiliated with or endorsed by OpenClaw Foundation or any platform.

Give OpenClaw your social accounts.

Add an account with a password, cookies or a sign-in link, then connect the MCP server and ask.