Actions15
Overview
This node queries the free/busy status of a calendar within a specified time range. It is useful for checking when a calendar is occupied or available, which can help in scheduling meetings, avoiding conflicts, or integrating calendar availability into workflows.
For example, you might use this node to:
- Determine if a user’s calendar has any events between two dates before scheduling a new event.
- Aggregate free/busy information from multiple calendars to find common available times.
- Trigger actions only when a calendar is free during a certain period.
Properties
| Name | Meaning |
|---|---|
| Calendar URL | The URL path of the calendar to query (e.g., /calendars/user@example.com/personal/). |
| Start Date & Time | The start datetime of the time range to check for free/busy status. |
| End Date & Time | The end datetime of the time range to check for free/busy status. |
Output
The node outputs JSON data representing the free/busy information for the specified calendar and time range. This typically includes details about busy periods within the queried interval.
If the calendar supports it, the output may include:
- Time slots marked as busy or free.
- Event details that cause the busy status.
No binary data output is indicated by the source code.
Dependencies
- Requires access to a CalDAV-compatible calendar service.
- Needs proper authentication credentials configured in n8n to access the calendar URL.
- The calendar URL must be valid and accessible with the provided credentials.
Troubleshooting
- Invalid Calendar URL: Ensure the calendar URL is correct and accessible.
- Authentication Errors: Verify that the API key or authentication token is properly set up and has permissions to read the calendar.
- Date Range Issues: Confirm that the start date/time is before the end date/time.
- Empty Results: If no busy times are returned, verify that there are events scheduled in the given time range.
Common error messages will likely relate to network issues, authentication failures, or invalid input parameters. Checking these areas usually resolves most problems.