Learn · Running an organization · 3 min read
Integrations
Wodo's integration list is short and we'd rather keep it honest than long: the things below work well.
Slack
Two directions:
- Activity into a channel. Map a space to a channel and choose which events post there — items created, labels changed, comments added. Each message links back to the item.
- Items out of messages. Right-click any Slack message → Create Wodo item. The message becomes an item in the space you choose — the "we should track that" moment, captured before it scrolls away.
Setup: an organization admin connects the workspace; each space's managers decide its channel and events. One caution worth knowing: anyone in your Slack workspace can use message → item creation for mapped spaces, so map spaces accordingly.
Microsoft Teams
The same two directions, with one extra: replying to a Wodo notification in Teams adds your reply as a comment on the item. The bot installs to your tenant via the standard admin consent flow.
AI assistants (MCP) — bring your own
Wodo speaks MCP, the open protocol AI tools use to work with other software. Open means exactly that: you bring the AI your company has approved, whatever it is — Mistral's Le Chat, a locally operated model on your own hardware, Claude, or any other MCP-capable assistant. We don't bundle an AI into Wodo, and we don't pick one for you. Your content, your choice of model — including the choice of none.
Once connected (and only with your explicit authorization), an assistant can search and read items and documents, create and update them, add comments, and manage labels and milestones — acting as you, seeing only what you can see. The access is scoped and revocable at any time, and an organization whose content is read-only is read-only for assistants too.
One honest reminder: what an assistant does with the content it reads is governed by its operator, not by us. That's exactly why the company-approved model — or the local one — is the right default.
Connecting takes one line of configuration pointing your assistant at Wodo's MCP endpoint, then an ordinary sign-in to authorize it:
