Overview
The "Get Single Event" operation of the iCloud Calendar node retrieves detailed information about a specific calendar event by its ID from a selected iCloud calendar. This operation is useful when you need to fetch all details of one particular event, such as for displaying event information, syncing with other systems, or processing event data in workflows.
Typical scenarios include:
- Fetching an event's full details to display in a custom dashboard.
- Retrieving event metadata for integration with CRM or project management tools.
- Using event data conditionally in automation workflows based on event properties.
Example: You want to get the details of a meeting scheduled in your iCloud calendar by providing the calendar and event IDs, then use that data to send reminders or update another system.
Properties
| Name | Meaning |
|---|---|
| Calendar Name or ID | Select the calendar from which to retrieve the event. You can choose from a list of available calendars or specify the calendar ID using an expression. This property is required. |
| Event ID | The unique identifier of the event to retrieve. This must be provided as a string. This property is required. |
Output
The output JSON contains the detailed information of the requested calendar event. The structure includes fields such as:
uid: Unique identifier of the event.summary: Title or summary of the event.description: Detailed description text of the event.location: Location where the event takes place.start,end: Start and end times of the event in original format.startIso,endIso: ISO 8601 formatted start and end timestamps.isAllDay: Boolean indicating if the event is an all-day event.status: Status of the event (e.g., confirmed, cancelled).sequence: Sequence number for event updates.timestamp: Timestamp of the event creation or last modification.rruleObject: Recurrence rule object if the event is recurring.url: URL associated with the event.invitees: List of attendees with their email, name, role, participation status, etc.attachments: List of attachments with URLs and MIME types.
This rich event data allows downstream nodes or workflows to fully understand and manipulate the event.
The node does not output binary data for this operation.
Dependencies
- Requires valid iCloud API credentials with username and password for CalDAV access.
- Uses HTTP requests to iCloud CalDAV endpoints.
- Depends on external libraries for XML parsing, date/time handling, and HTTP requests.
- Requires n8n environment to have network access to iCloud CalDAV servers.
Troubleshooting
- Authentication errors: If credentials are invalid or expired, the node will fail to authenticate with iCloud CalDAV. Recheck and update the API key credential.
- Invalid calendar or event ID: Providing incorrect calendar or event IDs will result in errors or empty responses. Verify IDs are correct and exist in the account.
- Network issues: Connectivity problems to iCloud servers may cause timeouts or failures. Ensure stable internet connection.
- Parsing errors: Malformed or unexpected calendar data might cause XML parsing errors. Usually rare but can happen if iCloud changes response formats.
- Error messages typically include HTTP status codes and error descriptions from iCloud. Review these messages to identify issues like permission denied, not found, or server errors.
Links and References
- CalDAV Protocol - Standard protocol used by iCloud Calendar.
- iCloud Calendar Integration Documentation - Apple official calendar help.
- n8n Expressions Documentation - For using expressions in property inputs.
This summary focuses specifically on the "Get Single Event" operation of the iCloud Calendar node as requested.