> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/plugins/integrations/communications/outlook.md). # Outlook With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Outlook and, when **Write** access is enabled, perform approved actions in Outlook. The Outlook integration connects a Microsoft 365 or Outlook.com account to Filed using Microsoft OAuth2. You authorize Filed through a standard Microsoft sign-in window; no password is entered into Filed directly. ## What this integration does When you connect Outlook, Filed opens a Microsoft sign-in window and requests permission scopes for IMAP access to your mailbox and the ability to send mail on your behalf, along with standard identity scopes. After you sign in and accept those permissions, Microsoft issues Filed a pair of tokens. Filed uses one token to read your mailbox over IMAP and a separate token to send messages through the Microsoft Graph API. Tokens are refreshed automatically in the background, so the connection remains active without requiring you to re-authorize periodically. Outbound messages sent through the Outlook integration are automatically saved to your Sent Items folder by Microsoft Graph. This is a built-in behavior of the Graph sending path and requires no additional configuration. The Outlook integration is designed for Microsoft 365 and Outlook.com accounts. On-premises Exchange servers that do not expose Microsoft OAuth are not supported; use the IMAP Email integration for those. ## Before you start You need a Microsoft 365 or Outlook.com account. If your organization manages Microsoft 365, confirm with your IT administrator that third-party app access is not blocked in your Azure AD tenant. If it is restricted, your administrator can approve Filed in the Azure AD app consent settings, or your firm can use the IMAP Email integration as an alternative. ## Connecting Outlook to Filed ## What Filed can do with Outlook **List mailboxes** - returns all folders available in the connected Outlook mailbox, including Inbox, Sent Items, Drafts, and any custom folders. **List messages** - retrieves an envelope listing of messages in any mailbox folder, with support for a keyword search query, a date filter (messages received after a given date), a maximum result count, and pagination using a continuation token. **Get message** - fetches the full content of a specific message identified by its mailbox path and UID. The response includes the subject, sender, recipients (To and CC), date, plain-text and HTML body, read/unread status, and a list of attachments with each attachment's filename, content type, and size. **Send message** - composes and sends a message from the connected Outlook account via the Microsoft Graph API. Supports To, CC, and BCC recipients, a subject, and a plain-text or HTML body. Sent messages are automatically saved to your Sent Items folder. ## Troubleshooting **Microsoft sign-in window does not open** - The sign-in flow opens in a pop-up window. If nothing appears, check that your browser is not blocking pop-ups for Filed and allow them if needed. **Access denied or admin approval required** - Your organization's Azure AD tenant may require administrator consent before users can authorize third-party applications. Ask your IT administrator to approve Filed in Azure AD, or switch to the IMAP Email integration which does not require Azure AD consent. **Connection shows an error after a password or account change** - Changing your Microsoft account password or certain account security events can invalidate the OAuth tokens Filed holds. Disconnect the integration and reconnect to issue fresh tokens. **Sent messages do not appear in Sent Items** - The Outlook integration sends via Microsoft Graph with the save-to-sent-items option enabled. If sent messages are missing, confirm that the Microsoft account connected in Filed matches the account you are checking in Outlook. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding Outlook information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Outlook data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find recent Outlook information related to \[client name] and summarize the key items.” * “Show me anything from the last 30 days that needs a response or follow-up.” * “With write access enabled, create the approved follow-up for \[client name] for my review.” ## Capabilities ### Review communication context Use Filed to retrieve the emails, calendar information, or meeting context available to the connected account. This helps your team find client follow-ups, deadlines, and outstanding requests. ### Coordinate approved follow-up When **Write** access is enabled, Filed can help create approved communications, events, or tasks supported by the provider. Use this for supervised follow-up workflows rather than unsupervised outreach. ### Keep access scoped to the right account The connection sees only what the authorized account can access. Use a firm-managed mailbox or calendar and its sharing settings to control scope. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.filed.com/reference/plugins/integrations/communications/outlook.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.