--- title: "OpenClaw" description: "Add the Rumoro skill to OpenClaw and ask it in plain words for your mentions, keywords, alerts and numbers." canonical: https://docs.rumoro.dev/integrations/openclaw markdown: https://docs.rumoro.dev/integrations/openclaw.mdx --- # OpenClaw Add the Rumoro skill to OpenClaw and ask it in plain words for your mentions, keywords, alerts and numbers. [OpenClaw](https://openclaw.ai) is a personal agent that runs on your own machine. With the `rumoro` skill it can answer "what did people say about us this week?" from your real mentions. It can also add keywords, close out mentions, set up alerts and read your analytics. You need a Rumoro API key and a running OpenClaw gateway. To connect without a key, add Rumoro's [MCP server](/mcp#openclaw) instead; the [OpenClaw page](https://rumoro.dev/openclaw) shows both. | | | | --- | --- | | Skill name | `rumoro` | | Install | `openclaw skills install @markolo10/rumoro --global` | | Key | `RUMORO_API_KEY` | | API | `https://api.rumoro.dev/v1` | What the skill lets OpenClaw do. | Area | For example | | --- | --- | | Keywords | Add brand, competitor and topic keywords, narrow noisy ones, read their health | | Mentions | Search with any filter, summarize, mark done or ignored, assign, snooze, correct a score | | People | Find the people with the most reach, tag them, log outreach | | Alerts | Instant alerts and hourly, daily or weekly digests to Slack, Telegram, email or a webhook | | Analytics | Summary, trends, breakdowns and share of voice | | Account | Balance, costs per keyword, the workspace the key belongs to | The skill is short. For anything it doesn't cover, it reads the [agent guide](https://mcp.rumoro.dev/mcp/guide) and the [OpenAPI document](https://api.rumoro.dev/v1/openapi.json), so it stays in step with the API. ## Step 1. Install the skill ```bash openclaw skills install @markolo10/rumoro --global ``` `--global` puts it in the shared skills folder that every agent on the machine reads. Leave it out to install into the current workspace only. Create a key on the [API keys](https://app.rumoro.dev) page. A `write` key covers the whole skill. A `read` key can search and read but change nothing. Then give it to OpenClaw, either in its environment file ```bash echo 'RUMORO_API_KEY=ref_...' >> ~/.openclaw/.env ``` or in `~/.openclaw/openclaw.json`, since the skill names `RUMORO_API_KEY` as its main variable. ```json5 { skills: { entries: { rumoro: { apiKey: "ref_..." }, }, }, } ``` If the gateway was already running, restart it so it reads the key. ```bash openclaw gateway restart openclaw skills check ``` Then ask OpenClaw something small. > Which Rumoro keywords do I have? It calls `GET /v1/keywords`. An empty list means the key works and nothing is tracked yet. ## Step 2. Ask Say what you want. The skill knows which calls to make. > Sum up this week's Hacker News talk about us. Which threads need a reply? OpenClaw asks for relevant Hacker News mentions from the past seven days, sorted by priority, and summarizes each one with the author, sentiment, intent and link. Other requests it handles. - "Add `driftwood` as a brand keyword and `netlify` as a competitor, limited to GitHub and Hacker News." - "Show bug reports from the last day, and mark the fixed ones done." - "Send negative mentions to the #support Slack channel as they come in." - "Email me a digest every weekday at 8:30 New York time." - "Which platforms brought the most mentions this month, and how do we compare with Netlify?" - "Find the ten most-followed people who mentioned us and tag the customers." - "This keyword is noisy. Check its health and fix it." Slack and Telegram channels are connected in the dashboard, so OpenClaw picks one you already have. It can create email and webhook channels itself. It asks you first before deleting anything, rotating a webhook secret or merging people. ## Step 3. Automate ### A morning summary An OpenClaw automation runs a prompt on a schedule and posts the answer to a channel. ```bash openclaw automations create "30 8 * * 1-5" \ "Use the rumoro skill. List the relevant mentions from the last 24 hours by sentiment, and point out questions and buying signals I should answer, with links." \ --name "Rumoro morning summary" \ --tz "America/New_York" \ --session isolated \ --announce \ --channel slack \ --to "channel:C0123456789" ``` Rumoro's own [daily digest](/alerts) sends the top mentions without an agent. Use the automation when you want OpenClaw's take, or a different question each morning. ### Answer a mention as it arrives A Rumoro [webhook channel](/webhooks) can wake OpenClaw for each mention. Turn on hooks in `~/.openclaw/openclaw.json` and add a mapping for Rumoro's payload. ```json5 { hooks: { enabled: true, token: "", path: "/hooks", mappings: [ { id: "rumoro", match: { path: "rumoro" }, action: "agent", name: "Rumoro {{event}}", messageTemplate: "New Rumoro mention on {{data.post.platform}} by {{data.author.name}}, sentiment {{data.classification.sentiment}}. {{data.post.text}} {{data.post.url}} Should we answer? Draft a reply.", deliver: true, channel: "slack", to: "channel:C0123456789", }, ], }, } ``` Run `openclaw config validate` and `openclaw gateway restart`. The hook URL has to be reachable over https from the internet, for example through a tunnel, because Rumoro can't reach `localhost`. Then ask OpenClaw to connect it. > Add a Rumoro webhook for https://gateway.example.com/hooks/rumoro that sends `Authorization: Bearer `, and alert it right away about every negative mention. Each negative mention now starts an OpenClaw run, and the draft appears in Slack. Rumoro counts any `2xx` answer within 10 seconds as delivered. OpenClaw wraps the post text as outside content before the model reads it, so leave `allowUnsafeExternalContent` off. ## If it fails **`401` from the API.** Check the key on the API keys page. If it is mistyped or revoked, fix it and restart the gateway. **The skill is missing.** `openclaw skills list` should show `rumoro`. If not, install it again. `openclaw skills check` names any missing requirement. **`403 read_only_key`.** Changes need a `write` key. Create one. **`402`.** The balance can't cover the change, such as one more keyword-day. Top up on the Billing page. Nothing is retried. **Sandboxed agents.** The key set in `skills.entries` only reaches agents that run on the host. Pass `RUMORO_API_KEY` to the sandbox separately. ## Related