Nodes
Read Outlook Events and Create Outlook Event have a Calendar field. Pick Default calendar or another calendar from the list, or bind a calendar
id from List Outlook Calendars.
Troubleshooting
Outlook calendar access was denied
Outlook calendar access was denied
For an OAuth connection, reconnect it and allow calendar access: reading needs Read calendars, creating and deleting need Create calendar events. For a service principal, an admin must grant the Microsoft Graph permission named in the error. See Connect Microsoft 365.
Outlook calendar or event not found
Outlook calendar or event not found
Check the selected Calendar, or the Event ID. A bound calendar ID must be an
id from List Outlook Calendars.End date must be on or after Start date
End date must be on or after Start date
In Read Outlook Events, set End date to the same day as Start date or later.
End must be after Start
End must be after Start
In Create Outlook Event, set End later than Start. Check Timezone when the values are bound without an offset.
... must be an ISO 8601 date or datetime
... must be an ISO 8601 date or datetime
A bound date is not in a format the node reads. Use a date such as
2025-08-08 or a date and time such as 2025-08-08T19:00:00.Read the first ... events; the range holds more
Read the first ... events; the range holds more
The range holds more events than Max events. Raise Max events, or narrow Start date and End date.
The event was created without a Teams meeting link
The event was created without a Teams meeting link
The event exists, but Outlook did not add a Teams meeting. Check that the connected Outlook account can create Teams meetings.
Outlook timed out. The event may have been created
Outlook timed out. The event may have been created
Open the calendar before you run the flow again, so you do not create or delete the event twice.