Problem
For many people, email and calendar are the single richest record of what they are working on: threads with decisions and context, commitments, meeting invites, and attendees. OpenWiki already supports Gmail, but there is no equivalent connector for Microsoft Outlook / Microsoft 365, which leaves a large group of enterprise users unable to bring their primary communication history in as a knowledge source.
Proposal
Add an optional Microsoft Outlook connector (Microsoft Graph API) covering mail and calendar, as a peer to the existing Gmail source.
It could support:
- Mail — importing messages and threads (conversations), subjects, bodies, participants, timestamps, folders/labels, and attachments, with links back to the source item
- Calendar — importing events, attendees, organizers, times, and descriptions, so meeting context is discoverable
- Incremental sync with configurable folders/mailboxes, time windows, and filtering/redaction controls
- Structuring imported content so people, projects, threads, and commitments are discoverable in OpenWiki
Auth / scope notes
This would use Microsoft Graph with delegated permissions such as Mail.Read and Calendars.Read. Reusing whatever OAuth/connector plumbing already backs Gmail (and the Teams request, if implemented) would keep the Microsoft 365 story consistent.
Example use case
My work lives in Outlook, not Gmail. Being able to connect it would let OpenWiki answer "what's the latest on this thread?" or "what did I commit to in that meeting?" grounded in my actual mail and calendar, with links back to the source.
Happy to help test or clarify the most useful mail/calendar fields and sync behavior.
Problem
For many people, email and calendar are the single richest record of what they are working on: threads with decisions and context, commitments, meeting invites, and attendees. OpenWiki already supports Gmail, but there is no equivalent connector for Microsoft Outlook / Microsoft 365, which leaves a large group of enterprise users unable to bring their primary communication history in as a knowledge source.
Proposal
Add an optional Microsoft Outlook connector (Microsoft Graph API) covering mail and calendar, as a peer to the existing Gmail source.
It could support:
Auth / scope notes
This would use Microsoft Graph with delegated permissions such as
Mail.ReadandCalendars.Read. Reusing whatever OAuth/connector plumbing already backs Gmail (and the Teams request, if implemented) would keep the Microsoft 365 story consistent.Example use case
My work lives in Outlook, not Gmail. Being able to connect it would let OpenWiki answer "what's the latest on this thread?" or "what did I commit to in that meeting?" grounded in my actual mail and calendar, with links back to the source.
Happy to help test or clarify the most useful mail/calendar fields and sync behavior.