--- title: "Outlook Integration" description: "Read, send, and organize email. Manage calendar events and contacts. Agents draft, send, forward, and reply to emails and create calendar events across Microsoft 365 accounts." url: https://flowrunner.ai/integrations/outlook date_modified: 2026-08-12T15:40:33-07:00 --- # Outlook [Email](https://flowrunner.ai/integrations/category/email-marketing) Read, send, and organize email. Manage calendar events and contacts. Agents draft, send, forward, and reply to emails and create calendar events across Microsoft 365 accounts. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 13 actions · OAuth · available [Outlook website](https://outlook.com/) · Capability data verified 2026-08-04 1. Scheduled run polls Get Messages List on dedicated operations inbox every 15 minutes 2. Agent classifies each email by type: invoice, PO confirmation, exception notification 3. Agent routes invoices to AP processing workflow via Parseur 4. Agent sends procurement a PO confirmation digest with Send Message 5. Agent marks anything it cannot classify as unread so it returns to the inbox 6. Ops channel receives processing summary with counts by category 7. Sensitive negotiations and complaint responses handled as drafts for human review and send ## What This Integration Enables Outlook integration lets agents operate inside Microsoft 365: sending emails from real organizational addresses, reading inbound messages for processing, creating and amending calendar events, and managing contacts. For organizations that run on Microsoft 365, agents operate as effective team members within the existing communication infrastructure. ### Without FlowRunner **Manual inbox triage**: Operations staff read every email in the shared inbox to classify and route it **Inbox checked intermittently**: Invoices and PO confirmations sit unprocessed until someone opens the inbox **Personal calendar entries**: Reps manually create meeting events in Outlook after each Calendly booking ### With FlowRunner **Inbox processed every 15 minutes**: New messages classified and routed before staff arrive in the morning **Zero manual routing**: Invoices, POs, and exceptions each flow to the right workflow automatically **Context-rich calendar events**: Meeting entries created with deal notes before the rep sees the booking notification ## Use Case Scenarios ### Inbound Email Processing A dedicated operations inbox receives vendor invoices, purchase order confirmations, and exception notifications. Every 15 minutes, an agent reads the inbox using Get Messages List. It classifies each email by type, routes invoices to the AP processing workflow (which hands off to Parseur), sends procurement a digest of the PO confirmations, and marks anything it cannot classify as unread so a person sees it. The inbox is processed before anyone arrives in the morning. ### Contract Execution Notification DocuSign's On Envelope Completed fires. The agent sends an email via Outlook to the newly contracted client from the account manager's real Microsoft 365 address: a personalized welcome message with their signed contract attached. The email appears to come from the account manager, strengthening the relationship. The account manager did not write it and does not need to. ### Meeting Scheduling from CRM A deal moves to Demo Scheduled in HubSpot. The agent creates a calendar event in the sales rep's Outlook calendar with the prospect's name, the Calendly meeting link, and the deal notes as the event body. The rep sees the meeting in their calendar with full context. No manual calendar entry required. ## Human-in-Loop Highlight When an agent is about to send an email from a person's real Microsoft 365 account, particularly for communications that require personal judgment (sensitive negotiations, escalation responses, customer complaints), it creates a draft instead of sending directly. It sends a Slack notification to the account owner: "I've drafted a response to \[Contact Name\]'s email. Review the draft here and send when ready, or I can send it automatically if no changes are needed within 2 hours." The person retains control over their voice. The agent does the writing. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 13 actions ### Email Operations 6 - **Send Message** Sends an email from the authenticated Microsoft 365 account, with subject, CC, and BCC. Used for all operational communication that needs to come from a real organizational address rather than a transactional email service. - **Reply to Message** Sends a reply on an existing message, keeping the thread intact. Used in automated response workflows where the agent answers a specific class of inbound mail in place rather than starting a new conversation. - **Create Draft Email** Creates an email draft without sending it. Used when an agent prepares a communication that a person will review, edit, and release under their own name. - **Send Draft Email** Sends a previously created draft by its ID. Used as the second half of the review-then-send pattern, after a human has approved the wording. - **Get Messages List** Returns messages from the mailbox with filtering by sender, subject, date range, and read status. Used in inbox monitoring workflows where agents classify and route inbound mail on a schedule. - **Mark Email As Unread** Marks a message unread. Used to hand a message back to a person deliberately: the agent has looked at it, decided it needs human eyes, and returns it to the inbox looking untouched. ### Calendar Management 4 - **Create Event** Creates a calendar event with subject, start and end time, time zone, location, description, and attendees. Used in scheduling workflows: a booking or a deal stage change produces the meeting entry with full context already in the body. - **Update Calendar Event** Modifies an existing event's subject, body, time, or attendee list. Used when meeting details change upstream and the calendar entry has to follow. - **Add Attendees to Calendar Event** Adds attendees to an existing event without overwriting the ones already on it. Used to pull a specialist into a scheduled meeting, which is the safe alternative to a full update that could silently drop the original invitee list. - **Delete Event** Removes a calendar event from every attendee's calendar. Used in cancellation workflows. ### Contacts 2 - **Create Contact** Creates a contact in the Outlook address book with name, email, phone, and company details. Used when new people enter operational workflows and the organization wants them reachable from Outlook rather than only from the CRM. - **Update Contact** Modifies an existing contact's details. Used to keep the address book synchronized with CRM or ERP data. ### Account 1 - **Get User Profile** Returns the signed-in user's Microsoft 365 profile, including display name and email. Used to resolve which mailbox and calendar a flow is actually operating on before it writes anything. ## Frequently Asked Questions ### What can FlowRunner do with Outlook? FlowRunner agents can run Get User Profile, Get Messages List, and Send Message in Outlook, plus 10 more actions. ### Does connecting Outlook to FlowRunner require OAuth? Yes. Outlook connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Outlook trigger a FlowRunner workflow automatically? Outlook doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Outlook?** This integration exposes Outlook to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/outlook. Site index: https://flowrunner.ai/llms.txt