Read Outlook calendar events, create and delete events, and pull event attachments.
| Category | โ Productivity |
| Connection | โก OAuth 2.0 one-click |
| Actions | 5 total โ 3 read, 2 write |
Once connected, Outlook Calendar exposes the following actions. The AI can call them with #-mentions in chat, an agent can be granted a subset as tools, and a workflow can run them in an integration-action node.
| Action | Type | What it does | Proxy |
|---|---|---|---|
Create Eventcreate-event | Write | Create a new Outlook calendar event, optionally as a Teams meeting with a join link. | Yes |
Delete Eventdelete-event | Write | Delete an Outlook calendar event by ID. | Yes |
Get Eventget-event | Read | Fetch a single Outlook calendar event by ID. | Yes |
Get Event Attachmentget-event-attachment | Read | Download one attachment of an Outlook calendar event whole and keep it as a document. Answers with the id, name, type and size of the stored document, never with the bytes of the file. | Yes |
List Eventslist-events | Read | List upcoming Outlook calendar events. | Yes |
Actions tagged Write create, update, or delete data. In chat and agent paths they pause for your confirmation before running; workflows treat their deterministic wiring as implicit consent. Agent tools covers how to scope which actions an agent may use.
Outlook Calendar is governed per organization: an admin sets a monetary spend cap and a monthly call quota. A quota of 0 disables the integration โ it never means unlimited. See the Integrations overview for the full governance model.