Calendar Tool Wrapper X

Wraps Microsoft Calendar Tool for AI operations
Join our community

Overview

This node acts as a wrapper around the Microsoft Calendar tool, specifically designed to retrieve calendar events. It fetches events from a specified calendar using Microsoft Outlook credentials and supports returning either all events or just the first page of results. This node is useful in automation workflows where you need to integrate calendar data, such as syncing events, generating reports, or triggering actions based on upcoming meetings.

Practical examples:

  • Automatically fetching all events from a team calendar to create a daily agenda.
  • Retrieving only the first page of events for quick previews or summaries.
  • Integrating calendar events into other systems like CRMs or project management tools.

Properties

Name Meaning
Calendar ID The identifier of the target calendar from which to retrieve events.
Return All Events Boolean option to specify whether to return all events or only the first page of results.

Output

The node outputs an array of event objects under the json field with the following structure for each event:

  • eventId: The unique identifier of the calendar event.
  • summary: The subject or title of the event.
  • start: The start time of the event.
  • end: The end time of the event.
  • calendar: The calendar ID from which the event was retrieved.

If no events are found, it returns an empty array under the key events.

Dependencies

  • Requires valid Microsoft Outlook API credentials (an OAuth2 token) configured in n8n.
  • Relies on the Microsoft Outlook API to fetch calendar events.
  • Uses an internal sub-workflow template (subWorkflowTemplate.json) to execute the Microsoft Calendar operation.

Troubleshooting

  • No credentials provided: The node will throw an error if Microsoft Outlook credentials are missing or invalid. Ensure that the API authentication token is correctly set up in n8n.
  • Empty event list: If no events are returned, verify that the Calendar ID is correct and that there are events within the queried timeframe.
  • API rate limits or connectivity issues: These may cause errors during execution. Check network connectivity and Microsoft API usage quotas.
  • Continue on Fail: If enabled, the node will output an error message in JSON format instead of failing the workflow.

Links and References

Discussion