Watched Channels
Opt Slack channels into review so Docpipe captures documentation-worthy messages automatically.
The /docpipe command captures knowledge one message at a time, on demand. Watched channels go further: Docpipe reviews the channels you choose on its own, finds the messages worth documenting, and turns them into proposals — without anyone running a command. It's the most hands-off way to keep your knowledge base current.
Before you start
- Your Slack workspace must be connected — see Connecting Slack.
- You need admin access: organization owner, or a role with the Manage org settings permission.
- Docpipe must be a member of each channel you want to watch. You can add it during setup, below.
Watch a channel
- Go to Settings → Integrations → Slack.
- Find the Watched channels card — "Capture documentation from messages in selected channels."
- Under Add a channel, search for the channel and select Watch.
If Docpipe is already in the channel, watching starts immediately. If it isn't, a dialog appears — "Docpipe is not in #channel" — because Docpipe has to be a member to read messages. You have two options:
- Add Docpipe automatically — Docpipe joins the channel for you.
- I'll add it myself — run
/invite @docpipein the channel, then come back.
Start with the channels where decisions and answers actually happen — an engineering channel, a support channel, an ops channel. Those produce the most documentation-worthy messages, so watching them is where automatic capture pays off most. You can always add more later.
Configure a watched channel
Each watched channel has two settings on its card in the Watching list.
Space
Space restricts which documents Docpipe tries to update from that channel.
- Leave it as No space mapping to let Docpipe choose the best destination across all spaces.
- Or point the channel at a specific space to keep its captures scoped — for example, map your support channel to your Support space so its messages only ever update support docs.
Approver
Approver is the person who receives a Slack DM to approve or reject each capture from that channel.
- The default is Org owner (default) — the organization owner gets the DMs.
- You can assign any teammate whose Slack account is linked to Docpipe. A good approver is someone close to the channel's subject, so they can judge proposals quickly.
The card shows a plain-language summary of both settings, so you can see at a glance where a channel's captures go and who reviews them.
What happens after you watch a channel
Once a day, Docpipe reviews the new messages in each watched channel and does three things:
- Filters out everyday chatter — greetings, reactions, and back-and-forth that isn't documentation.
- Extracts only the content worth keeping, grouping related messages into candidate updates.
- Proposes a change for each one and sends the channel's approver a Slack DM with the proposal and Approve, Edit, and Reject buttons.
Because a person reviews every proposal before it's saved, watching a channel never writes to your documentation on its own. The review step is the same one described in Reviewing proposals.
Stop watching a channel
To turn a channel off, select Stop watching on its card. Docpipe stops reviewing it right away. Anything already captured from it is unaffected, and Docpipe stays in the channel — remove it in Slack if you want it gone entirely.
Watched channels vs. /docpipe
Both feed the same proposal-and-review flow, but they suit different moments:
| /docpipe | Watched channels | |
|---|---|---|
| Triggered by | A person running the command | Docpipe, on a daily schedule |
| What's captured | The exact message you send | Documentation-worthy messages Docpipe finds |
| Approval goes to | The channel it was run in | The channel's designated approver, by DM |
| Best for | A specific decision you know is worth keeping | Catching what would otherwise slip by |
Most teams use both: /docpipe for the things people know are worth keeping, and watched channels to catch the rest.
If watched channels shows a permissions error, Docpipe's Slack access needs refreshing — reconnect Slack from the same page. See Connecting Slack.