ClawLink
TL;DR
| Question | Answer |
|---|---|
| What does it do? | Your agent finds the Slack channel, reads today's messages and gives you a digest: what was decided, what questions are open and where you were mentioned. |
| Who is it for? | People in busy channels who check Slack a few times a day, not all day. |
| What do I connect? | Slack, once, with its own sign-in. ClawLink never sees your password. |
| What does it cost? | About 2 tool calls on your plan. Starter includes 1,000 a month. |
| Does it work? | slack_fetch_conversation_history succeeded on 99.7% of 2,305 calls on ClawLink in the last 30 days. |
| Which agents? | OpenClaw, Hermes, Claude, Codex, ChatGPT and any MCP client connected to ClawLink. |
How do you try it?
- Set up ClawLink once. Add it to your agent from the install page, then connect Slack.
- Send this prompt to your agent. Click the card to copy it.
It works the same in OpenClaw, Hermes, Claude and Codex.
How does the agent do it?
The agent makes 2 calls through ClawLink. You do not pick the tools: the agent finds them by searching ClawLink, reads their input schema and runs them.
| Step | Tool | What it does | Calls in 30 days |
|---|---|---|---|
| 1 | slack_find_channels | Finds the channel id from its name. | New |
| 2 | slack_fetch_conversation_history | Reads messages in a time range. | 2,305 (99.7% ok) |
How often does this work on ClawLink?
We do not publish a sample run for this job: its output is somebody's own Slack. Instead, here is how the same tools performed for every ClawLink user from 2026-09-03 to 2026-10-03. A call counts as failed only when it reached Slack and came back with an error.
| Tool | Calls | Users | Succeeded | Average time |
|---|---|---|---|---|
slack_fetch_conversation_history | 2,305 | 3 | 99.7% | 1.8 s |
How do you write the prompt?
- Name the channel. "#general" or "#product"; the agent looks up the id.
- Ask for open questions. The most useful part of a digest.
- Several channels. List them; each is one read.
What can go wrong?
- Threads. Replies in threads need extra reads. Ask the agent to open busy threads.
- Private channels. The agent can read only channels your Slack connection can see.
- Long days. A very busy channel returns pages of messages. Ask for a time window.
How does this compare with other ways to do it?
| Option | How it works | Cost | Best for |
|---|---|---|---|
| ClawLink + your agent | One prompt, a digest | 2+ tool calls on your plan | Catching up from your agent |
| Slack AI recaps | Built into Slack | Paid Slack add-on | Teams already paying for it |
| Scroll the channel | By hand | Free | Quiet channels |
Frequently asked questions
Can it post the digest to Slack?
Yes, the agent can send it to a channel you name, after you confirm.
Does it read DMs?
Only conversations your connection can access.
Does ClawLink keep the messages?
No.
What does it cost?
Two or more tool calls on your plan.
Can it run every evening?
Yes, schedule the prompt.