For the complete documentation index, see llms.txt. This page is also available as Markdown.

Microsoft Outlook Calendar

Microsoft Outlook Calendar integration in Lleverage connects your workflows and agents to your calendar, so they can schedule and manage events, keep other systems in sync, and react automatically when the calendar changes.

How to Connect

  1. Go to Settings > Connections in your project

  2. Pick Microsoft Outlook Calendar from the list of apps

  3. Choose which actions the connection should allow and who should have access (shared or personal)

  4. Choose "Connect Now" and sign in with Microsoft, or send an authentication link so a colleague can connect on your behalf

Connecting without an individual account

Outlook Calendar also supports service-to-service access using an app registration your IT team creates in Microsoft Azure. Choose "App Registration (S2S)" in the connect dialog and enter the Client ID, Client Secret and Tenant ID, or send a secure link to your IT administrator so they can enter the details themselves.

💡 If your Microsoft organisation requires administrator approval for new apps, the connect flow gives you an approval link to share with your Microsoft administrator.

What Outlook Calendar Can Do

  • Events - create, update and delete events, and retrieve a single event's details

  • Browsing - list events over a period and list the calendars in the account

  • Responding - accept, decline or tentatively accept an event invitation

Triggers

Outlook Calendar provides three triggers, so workflows can start automatically when:

  • An event is created

  • An event is updated

  • An event is cancelled

Microsoft notifies Lleverage when these events happen, so workflows start straight away.

💡 Use case: Prepare a briefing document before every external meeting, sync calendar changes to a project tracker, or notify the team when a key meeting is cancelled.

Important Considerations

  • The connection works with the calendars the signed-in account can access

  • With service-to-service access, actions can work with any user's calendar in your organisation, so keep the connection's action policy tight

Last updated

Was this helpful?