Publish your Slack docs to GitHub, Notion, or Confluence
Capturing a Slack thread as a clean document is only half the job. The other half is putting it where your team already looks — your repo, your workspace, or your wiki. A doc in the wrong tool is a doc nobody reads.
Knowledge Grabber connects to three destinations, and you choose which one each document goes to.
Connect once, in Settings
Each destination uses a secure, official connect flow — no tokens pasted by hand:
- GitHub — install the GitHub App and pick a repository, branch, and docs folder. Approved docs are committed as Markdown files, so they're versioned and reviewable in a pull request.
- Notion — connect via OAuth and share a page with the integration. Docs are published as clean child pages under it, searchable across your workspace.
- Confluence — authorize through Atlassian OAuth and we publish pages straight into your Confluence space, right next to your existing runbooks.
If a destination isn't configured, its connect button simply doesn't appear — no dead ends.
Pick a destination per document
You don't have to commit the whole team to one tool. Connect all three, and on each document choose Publish to → GitHub / Notion / Confluence from a dropdown. Engineering docs can go to the repo; incident write-ups can go to Confluence; team FAQs can go to Notion.
Everything stays reviewed
Whichever destination you choose, the flow is the same: the AI drafts, you approve, and only then does it publish. Your repo and wiki never fill up with unreviewed AI output.
The payoff
Your knowledge lands in the search your team already runs — Git, Notion, or Confluence — instead of a separate silo. That's the difference between documentation that gets read and documentation that rots.