Outlook Calendar
Like Google Calendar, Outlook Calendar is an agent tool, not a call trigger. Connect it once per workspace via OAuth2, then attach it to an agent so it can check availability and book, move, or cancel an appointment while the caller is still on the line.
Connecting
From Integrations, connect Outlook Calendar. This uses the standard Microsoft OAuth2 consent screen, scoped to User.Read, Calendars.ReadWrite and offline_access — just enough to read and write the connected calendar, with offline_access covering silent token renewal (see Token refresh). It works with both a Microsoft 365/work account and a personal Outlook.com account.
Configuring the tool
When attaching Outlook Calendar to an agent, configure:
| Field | Required | Description |
|---|---|---|
calendar_id | No | An email address if the agent should check/book a specific mailbox. Left blank, it resolves to whichever Microsoft account was connected. |
timezone | No | Default timezone for events this tool creates. |
duration_minutes | No | Default appointment length when the agent doesn't supply an end time. |
Actions
| Action | What it does | Arguments the agent supplies |
|---|---|---|
check_availability | Reads busy periods over a time range | time_min, time_max (both optional, default to now → +7 days) |
create_event | Books an event | summary, start (required); end, duration_minutes, description, attendees (optional) |
cancel_event | Cancels an existing event | event_id |
Availability is read live via Microsoft Graph's getSchedule at the moment the agent checks, not from a cached copy — so the time it offers is genuinely free when it offers it.
Token refresh
Access tokens are refreshed automatically a few minutes before they expire, the same as every other OAuth2-connected calendar. If refresh ever fails (the grant was revoked, or the password changed on the Microsoft side), the tool returns a message asking the user to reconnect rather than failing silently mid-call.