outlook-calendar-automation
npx machina-cli add skill davepoon/buildwithclaude/outlook-calendar-automation --openclawOutlook Calendar Automation via Rube MCP
Automate Outlook Calendar operations through Composio's Outlook toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/outlook
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Outlook connection via
RUBE_MANAGE_CONNECTIONSwith toolkitoutlook - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitoutlook - 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 titlestart_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 objectsbody: Event description (plain text or HTML)is_html: Set true if body contains HTMLlocation: Physical location stringis_online_meeting: Set true for Teams meeting linkonline_meeting_provider: 'teamsForBusiness' for Teams integrationshow_as: 'free', 'tentative', 'busy', 'oof'
Pitfalls:
- start_datetime must be chronologically before end_datetime
- time_zone is required and must be a valid IANA or Windows timezone name
- Adding attendees can trigger invitation emails immediately
- To generate a Teams meeting link, set BOTH is_online_meeting=true AND online_meeting_provider='teamsForBusiness'
- user_id defaults to 'me'; use email or UUID for other users' calendars
2. List and Search Events
When to use: User wants to find events on their calendar
Tool sequence:
OUTLOOK_GET_MAILBOX_SETTINGS- Get user timezone for accurate queries [Prerequisite]OUTLOOK_LIST_EVENTS- Search events with filters [Required]OUTLOOK_GET_EVENT- Get full details for a specific event [Optional]OUTLOOK_GET_CALENDAR_VIEW- Get events active during a time window [Alternative]
Key parameters:
filter: OData filter string (e.g., "start/dateTime ge '2024-07-01T00:00:00Z'")select: Array of properties to returnorderby: Sort criteria (e.g., ['start/dateTime desc'])top: Results per page (1-999)timezone: Display timezone for resultsstart_datetime/end_datetime: For CALENDAR_VIEW time window (UTC with Z suffix)
Pitfalls:
- OData filter datetime values require single quotes and Z suffix
- Use 'start/dateTime' for event start filtering, NOT 'receivedDateTime' (that is for emails)
- 'createdDateTime' supports orderby/select but NOT filtering
- Pagination: follow @odata.nextLink until all pages are collected
- CALENDAR_VIEW is better for "what's on my calendar today" queries (includes spanning events)
- LIST_EVENTS is better for keyword/category filtering
- Response events have start/end nested as start.dateTime and end.dateTime
3. Update Events
When to use: User wants to modify an existing calendar event
Tool sequence:
OUTLOOK_LIST_EVENTS- Find the event to update [Prerequisite]OUTLOOK_UPDATE_CALENDAR_EVENT- Update the event [Required]
Key parameters:
event_id: Unique event identifier (from LIST_EVENTS)subject: New event title (optional)start_datetime/end_datetime: New times (optional)time_zone: Timezone for new timesattendees: Updated attendee list (replaces existing if provided)body: Updated description with contentType and contentlocation: Updated location
Pitfalls:
- UPDATE merges provided fields with existing event; unspecified fields are preserved
- Providing attendees replaces the ENTIRE attendee list; include all desired attendees
- Providing categories replaces the ENTIRE category list
- Updating times may trigger re-sends to attendees
- event_id is required; obtain from LIST_EVENTS first
4. Delete Events and Decline Invitations
When to use: User wants to remove an event or decline a meeting invitation
Tool sequence:
OUTLOOK_DELETE_EVENT- Delete an event [Optional]OUTLOOK_DECLINE_EVENT- Decline a meeting invitation [Optional]
Key parameters:
event_id: Event to delete or declinesend_notifications: Send cancellation notices to attendees (default true)comment: Reason for declining (for DECLINE_EVENT)proposedNewTime: Suggest alternative time when declining
Pitfalls:
- Deletion with send_notifications=true sends cancellation emails
- Declining supports proposing a new time with start/end in ISO 8601 format
- Deleting a recurring event master deletes all occurrences
- sendResponse in DECLINE_EVENT controls whether the organizer is notified
5. Find Available Meeting Times
When to use: User wants to find optimal meeting slots across multiple people
Tool sequence:
OUTLOOK_FIND_MEETING_TIMES- Get meeting time suggestions [Required]OUTLOOK_GET_SCHEDULE- Check free/busy for specific people [Alternative]
Key parameters:
attendees: Array of attendee objects with email and typemeetingDuration: ISO 8601 duration (e.g., 'PT1H' for 1 hour, 'PT30M' for 30 min)timeConstraint: Time slots to search withinminimumAttendeePercentage: Minimum confidence threshold (0-100)Schedules: Email array for GET_SCHEDULEStartTime/EndTime: Time window for schedule lookup (max 62 days)
Pitfalls:
- FIND_MEETING_TIMES searches within work hours by default; use activityDomain='unrestricted' for 24/7
- Time constraint time slots require dateTime and timeZone for both start and end
- GET_SCHEDULE period cannot exceed 62 days
- Meeting suggestions respect attendee availability but may return suboptimal times for complex groups
Common Patterns
Event ID Resolution
1. Call OUTLOOK_LIST_EVENTS with time-bound filter
2. Find target event by subject or other criteria
3. Extract event id (e.g., 'AAMkAGI2TAAA=')
4. Use in UPDATE, DELETE, or GET_EVENT calls
OData Filter Syntax for Calendar
Time range filter:
filter: "start/dateTime ge '2024-07-01T00:00:00Z' and start/dateTime le '2024-07-31T23:59:59Z'"
Subject contains:
filter: "contains(subject, 'Project Review')"
Combined:
filter: "contains(subject, 'Review') and categories/any(c:c eq 'Work')"
Timezone Handling
- Get user timezone:
OUTLOOK_GET_MAILBOX_SETTINGSwith select=['timeZone'] - Use consistent timezone in filter datetime values
- Calendar View requires UTC timestamps with Z suffix
- LIST_EVENTS filter accepts timezone in datetime values
Online Meeting Creation
1. Set is_online_meeting: true
2. Set online_meeting_provider: 'teamsForBusiness'
3. Create event with OUTLOOK_CALENDAR_CREATE_EVENT
4. Teams join link available in response onlineMeeting field
5. Or retrieve via OUTLOOK_GET_EVENT for the full join URL
Known Pitfalls
DateTime Formats:
- ISO 8601 format required: '2025-01-03T10:00:00'
- Calendar View requires UTC with Z: '2025-01-03T10:00:00Z'
- Filter values need single quotes: "'2025-01-03T00:00:00Z'"
- Timezone mismatches shift event boundaries; always resolve user timezone first
OData Filter Errors:
- 400 Bad Request usually indicates filter syntax issues
- Not all event properties support filtering (createdDateTime does not)
- Retry with adjusted syntax/bounds on 400 errors
- Valid filter fields: start/dateTime, end/dateTime, subject, categories, isAllDay
Attendee Management:
- Adding attendees triggers invitation emails
- Updating attendees replaces the full list; include all desired attendees
- Attendee types: 'required', 'optional', 'resource'
- Calendar delegation affects which calendars are accessible
Response Structure:
- Events nested at response.data.value
- Event times at event.start.dateTime and event.end.dateTime
- Calendar View may nest at data.results[i].response.data.value
- Parse defensively with fallbacks for different nesting levels
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| Create event | OUTLOOK_CALENDAR_CREATE_EVENT | subject, start_datetime, end_datetime, time_zone |
| List events | OUTLOOK_LIST_EVENTS | filter, select, top, timezone |
| Get event details | OUTLOOK_GET_EVENT | event_id |
| Calendar view | OUTLOOK_GET_CALENDAR_VIEW | start_datetime, end_datetime |
| Update event | OUTLOOK_UPDATE_CALENDAR_EVENT | event_id, subject, start_datetime |
| Delete event | OUTLOOK_DELETE_EVENT | event_id, send_notifications |
| Decline event | OUTLOOK_DECLINE_EVENT | event_id, comment |
| Find meeting times | OUTLOOK_FIND_MEETING_TIMES | attendees, meetingDuration |
| Get schedule | OUTLOOK_GET_SCHEDULE | Schedules, StartTime, EndTime |
| List calendars | OUTLOOK_LIST_CALENDARS | user_id |
| Mailbox settings | OUTLOOK_GET_MAILBOX_SETTINGS | select |
Powered by Composio
Source
git clone https://github.com/davepoon/buildwithclaude/blob/main/plugins/all-skills/skills/outlook-calendar-automation/SKILL.mdView on GitHub Overview
Automate Outlook Calendar tasks using Composio's Outlook toolkit via Rube MCP. It covers creating events, managing attendees, finding meeting times, and handling invitations. Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
How This Skill Works
The skill connects to Rube MCP as an MCP server and requires an active Outlook connection. It uses a sequence of Outlook tool calls (e.g., OUTLOOK_LIST_CALENDARS, OUTLOOK_CALENDAR_CREATE_EVENT, OUTLOOK_LIST_EVENTS) with parameters like subject, start_datetime, end_datetime, time_zone, attendees_info, and is_online_meeting. For Teams meetings, set is_online_meeting to true and online_meeting_provider to teamsForBusiness. Ensure authentication and connection status are ACTIVE before workflow execution.
When to Use It
- Schedule a new calendar event with attendees and an optional Teams meeting
- Find events within a date range or by keywords
- Update details of an existing calendar event (time, title, attendees)
- List calendars and create events in a specific calendar
- Get a calendar view for today or a defined time window to see what's scheduled
Quick Start
- Step 1: Verify Rube MCP is available by calling RUBE_SEARCH_TOOLS
- Step 2: Connect Outlook with RUBE_MANAGE_CONNECTIONS using toolkit 'outlook'
- Step 3: Create a calendar event with OUTLOOK_CALENDAR_CREATE_EVENT (provide subject, start_datetime, end_datetime, time_zone, attendees_info, and optional is_online_meeting)
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
- Validate time_zone and use ISO 8601 timestamps (start_datetime, end_datetime)
- Ensure start_datetime is before end_datetime to avoid errors
- Adding attendees may trigger invitation emails immediately
- To create a Teams meeting, set is_online_meeting to true and online_meeting_provider to teamsForBusiness
Example Use Cases
- Create a 60-minute team sync tomorrow from 10:00 to 11:00 in 'Pacific Standard Time' with attendees and a location
- Schedule a client call with a Teams link by setting is_online_meeting=true and online_meeting_provider=teamsForBusiness
- List all events in the next 7 days with a keyword filter like 'quarterly review'
- Update an existing event's time to 2:00 PM and change the location to 'Conference Room B'
- Get today's calendar view to show all events spanning the current day
Frequently Asked Questions
Related Skills
ansible
chaterm/terminal-skills
Ansible 自动化运维
shell-scripting
chaterm/terminal-skills
Bash Shell 脚本编写
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
cron
chaterm/terminal-skills
定时任务管理
programmatic-seo
coreyhaines31/marketingskills
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
Playwright Browser Automation
jpulido240-svg/playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.