Outlook Automation

# Outlook Automation via Rube MCP

Automate Microsoft Outlook operations through Composio's Outlook toolkit via Rube MCP.

Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)

- Active Outlook connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `outlook`

- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

Setup

**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds

2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `outlook`

3. If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth

4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Search and Filter Emails

**When to use**: User wants to find specific emails across their mailbox

**Tool sequence**:

1. `OUTLOOK_SEARCH_MESSAGES` - Search with KQL syntax across all folders [Required]

2. `OUTLOOK_GET_MESSAGE` - Get full message details [Optional]

3. `OUTLOOK_LIST_OUTLOOK_ATTACHMENTS` - List message attachments [Optional]

4. `OUTLOOK_DOWNLOAD_OUTLOOK_ATTACHMENT` - Download attachment [Optional]

**Key parameters**:

- `query`: KQL search string (from:, to:, subject:, received:, hasattachment:)

- `from_index`: Pagination start (0-based)

- `size`: Results per page (max 25)

- `message_id`: Message ID (use hitId from search results)

**Pitfalls**:

- Only works with Microsoft 365/Enterprise accounts (not @hotmail.com/@outlook.com)

- Pagination relies on hitsContainers[0].moreResultsAvailable; stop only when false

- Use hitId from search results as message_id for downstream calls, not resource.id

- Index latency: very recent emails may not appear immediately

- Inline images appear as attachments; filter by mimetype for real documents

2. Query Emails in a Folder

**When to use**: User wants to list emails in a specific folder with OData filters

**Tool sequence**:

1. `OUTLOOK_LIST_MAIL_FOLDERS` - List mail folders to get folder IDs [Prerequisite]

2. `OUTLOOK_QUERY_EMAILS` - Query emails with structured filters [Required]

**Key parameters**:

- `folder`: Folder name ('inbox', 'sentitems', 'drafts') or folder ID

- `filter`: OData filter (e.g., `isRead eq false and importance eq 'high'`)

- `top`: Max results (1-1000)

- `orderby`: Sort field and direction

- `select`: Array of fields to return

**Pitfalls**:

- QUERY_EMAILS searches a SINGLE folder only; use SEARCH_MESSAGES for cross-folder search

- Custom folders require folder IDs, not display names; use LIST_MAIL_FOLDERS

- Always check response['@odata.nextLink'] for pagination

- Cannot filter by recipient or body content; use SEARCH_MESSAGES for that

3. Manage Calendar Events

**When to use**: User wants to list, search, or inspect calendar events

**Tool sequence**:

1. `OUTLOOK_LIST_EVENTS` - List events with filters [Optional]

2. `OUTLOOK_GET_CALENDAR_VIEW` - Get events in a time window [Optional]

3. `OUTLOOK_GET_EVENT` - Get specific event details [Optional]

4. `OUTLOOK_LIST_CALENDARS` - List available calendars [Optional]

5. `OUTLOOK_GET_SCHEDULE` - Get free/busy info [Optional]

**Key parameters**:

- `filter`: OData filter (use start/dateTime, NOT receivedDateTime)

- `start_datetime`/`end_datetime`: ISO 8601 for calendar view

- `timezone`: IANA timezone (e.g., 'America/New_York')

- `calendar_id`: Optional non-primary calendar ID

- `select`: Fields to return

**Pitfalls**:

- Use calendar event properties only (start/dateTime, end/dateTime), NOT email properties (receivedDateTime)

- Calendar view requires start_datetime and end_datetime

- Recurring events need `expand_recurring_events=true` to see individual occurrences

- Decline status is per-attendee via attendees[].status.response

4. Manage Contacts

**When to use**: User wants to list, create, or organize contacts

**Tool sequence**:

1. `OUTLOOK_LIST_CONTACTS` - List contacts [Optio