Problem
A large share of day-to-day work context lives in Microsoft Teams: decisions made in channel threads, questions answered in chats, meeting discussions, and shared files. For anyone using OpenWiki as a personal or team knowledge base, this is high-value context that is currently invisible to the agent — there is no way to bring Teams activity in as a knowledge source.
Proposal
Add an optional Microsoft Teams connector (Microsoft Graph API) that can import and incrementally sync Teams content into OpenWiki.
It could support:
- Selecting one or more teams/channels and, optionally, 1:1 and group chats
- Importing messages, threaded replies, mentions, reactions, timestamps, authors, and links back to the source message
- Meeting context where available (chat, shared files, and transcripts/recordings when the tenant enables them)
- Incremental sync with configurable time windows, channel/chat allowlists, and redaction controls
- Structuring imported content so topics, decisions, and recurring discussions are discoverable in OpenWiki
Auth / scope notes
Teams is Microsoft 365, so this would use Microsoft Graph with delegated (or application) permissions such as Channel.ReadBasic.All, ChannelMessage.Read.All, and Chat.Read. Admin consent and tenant policies vary, so per-team/per-channel selection and clear scope documentation would matter.
Example use case
Most of my team's real decisions happen in Teams threads, not in docs. Connecting Teams to OpenWiki would let me ask "what did we decide about X and why?" and get an answer grounded in the actual conversation, with a link back to it.
Happy to help test or clarify the most useful message/meeting fields and sync behavior.
Problem
A large share of day-to-day work context lives in Microsoft Teams: decisions made in channel threads, questions answered in chats, meeting discussions, and shared files. For anyone using OpenWiki as a personal or team knowledge base, this is high-value context that is currently invisible to the agent — there is no way to bring Teams activity in as a knowledge source.
Proposal
Add an optional Microsoft Teams connector (Microsoft Graph API) that can import and incrementally sync Teams content into OpenWiki.
It could support:
Auth / scope notes
Teams is Microsoft 365, so this would use Microsoft Graph with delegated (or application) permissions such as
Channel.ReadBasic.All,ChannelMessage.Read.All, andChat.Read. Admin consent and tenant policies vary, so per-team/per-channel selection and clear scope documentation would matter.Example use case
Most of my team's real decisions happen in Teams threads, not in docs. Connecting Teams to OpenWiki would let me ask "what did we decide about X and why?" and get an answer grounded in the actual conversation, with a link back to it.
Happy to help test or clarify the most useful message/meeting fields and sync behavior.