IntegrationSlack

Turn Slack threads into lasting project knowledge.

@-mention Odin or DM the bot. Important conversations land in your project Raw and can flow into the wiki on ingest.

  • Only activity through the Odin app (not full workspace scraping)
  • Smart thread summaries after a short quiet period
  • Same access labels as the web app when teammates link Slack identity
  • Chat in Slack with wiki and connected tools
All integrationsHow Odin works

In Odin

Saved snapshot (Raw)
Yes
Live in chat
No
How it works

From connect to project knowledge

  1. Install the Odin Slack app per workspace (one workspace per Odin project).
  2. Qualifying @-mentions and DMs become Raw notes with a path per message.
  3. After a thread goes quiet, Odin may roll busy threads into one summary and remove per-message notes.
  4. Run Ingest on saved Raw, or compile from the full corpus, to fold Slack into the wiki.
  5. The Slack bot answers using the same wiki and connected tools as the web app.
Why Odin

Why Slack makes Odin better

  • Decisions in flow of work: capture threads where they happen, not in a separate doc tool.
  • Noise control: Odin decides whether a thread deserves a summary before it enters the corpus.
  • Compounding context: Slack joins repo, tickets, and design in one wiki.
Good to know

Odin does not search all of Slack history from the panel. It does not auto-post wiki edits to channels.

Project wiki

Part of one compounding knowledge layer

Odin maintains a persistent project wiki that compounds over time. Integrations write to Raw, ingest and compile turn that into durable linked knowledge, and chat answers using the wiki first with live tools when freshness matters.

Slack

Stop losing decisions in scrollback.

Connect Slack under Project → Integrations. Odin saves what you choose, turns it into project knowledge, and answers in chat using what is connected.

All integrationsHow Odin works