| name | outlook-calendar-automation |
| description | Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | productivity |
| category | automation |
| risk | critical |
| source | community |
| tags | ["skill","productivity","automation","outlook","calendar"] |
Outlook Calendar Automation via Rube MCP
Automate Outlook Calendar 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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit outlook
- If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create Calendar Events
When to use: User wants to schedule a new event on their Outlook calendar
Tool sequence:
OUTLOOK_LIST_CALENDARS - List available calendars [Optional]
OUTLOOK_CALENDAR_CREATE_EVENT - Create the event [Required]
Key parameters:
subject: Event title
start_datetime: ISO 8601 start time (e.g., '2025-01-03T10:00:00')
end_datetime: ISO 8601 end time (must be after start)
time_zone: IANA or Windows timezone (e.g., 'America/New_York', 'Pacific Standard Time')
attendees_info: Array of email strings or attendee objects
body: Event description (plain text or HTML)
is_html: Set true if body contains HTML
location: Physical location string
is_online_meeting: Set true for Teams meeting link
online_meeting_provider: 'teamsForBusiness' for Teams integration
show_as: 'free', 'tentative', 'busy', 'oof'
Pitfalls:
- start_datetime must be chronologically before end_datetime