Actions9
- Message Actions
- Calendar Actions
- SharePoint Actions
Overview
The node provides functionality to update an existing calendar event in a Microsoft Outlook calendar. It allows users to modify key details of an event such as the subject, timing, location, description, importance, availability status, reminders, and attendees.
This node is beneficial in automation workflows where calendar events need to be programmatically updated based on external triggers or data changes. For example, it can be used to synchronize event details from another system, adjust meeting times dynamically, or update attendee lists automatically.
Practical examples:
- Automatically updating a meeting's time and location when a project deadline shifts.
- Adding or removing attendees based on changes in team membership.
- Adjusting reminder settings for important events created by other systems.
Properties
| Name | Meaning |
|---|---|
| Calendar | The calendar in which the event exists (selectable from available calendars). |
| Event ID | The unique identifier of the event to update. |
| Subject | The title or subject of the event. |
| All Day Event | Whether the event lasts all day (true/false). |
| Time Zone | The time zone for the event's start and end times. Options include UTC, Europe/Warsaw, America/New_York, Asia/Tokyo, etc. |
| Start Date & Time | The starting date and time of the event. For all-day events, only the date part is considered. |
| End Date & Time | The ending date and time of the event. For all-day events, only the date part is considered. |
| Location | The physical or virtual location of the event. |
| Body | A textual description or notes about the event. |
| Importance | The importance level of the event: Low, Normal, or High. |
| Show As | Availability status during the event: Free, Tentative, Busy, Out of Office, or Working Elsewhere. |
| Enable Reminder | Whether to enable a reminder notification for the event (true/false). |
| Reminder Time | The amount of time before the event when the reminder should trigger (numeric value). |
| Time Unit | The unit of time for the reminder: Minutes, Hours, Days, or Weeks. |
| Attendees | Comma-separated list of email addresses of event participants (e.g., user1@example.com,user2@example.com). |
Output
The output JSON contains the updated event object returned from the Microsoft Graph API after the PATCH request. This includes updated fields such as subject, start and end times, location, attendees, and other event metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an authenticated connection to Microsoft Graph API with permissions to access and modify calendar events.
- The node depends on an API authentication token configured in n8n credentials to authorize requests.
- The node uses internal helper functions to make HTTP PATCH requests to the
/me/calendars/{calendarId}/events/{eventId}endpoint.
Troubleshooting
- Date Parsing Errors: If the start or end date/time values are invalid or cannot be parsed, the node will throw an error indicating failure to parse dates. Ensure that date/time inputs are correctly formatted ISO strings or valid date objects.
- Invalid Event ID: Providing a non-existent or incorrect event ID will cause the API call to fail. Verify the event ID corresponds to an existing event in the selected calendar.
- Permission Issues: Insufficient permissions or expired tokens may result in authorization errors. Confirm that the API credentials have calendar write permissions.
- API Errors: Any errors returned by the Microsoft Graph API (e.g., rate limits, malformed requests) will be logged and surfaced by the node. Review the error message and response details for troubleshooting.