RFCALENDAR: Get Event Details

Get detailed information about a specific calendar event from RFCALENDAR

Overview

This node retrieves detailed information about a specific calendar event from the RFCALENDAR service using the event's unique identifier (UUID). It is useful when you need to fetch comprehensive details of an event, such as its summary, description, start and end times, and recurrence rules. Typical use cases include synchronizing event data with other systems, displaying event details in custom dashboards, or processing event information for notifications.

Properties

Name Meaning
Operation Mode Choose whether to use the API key stored in the node's credential or provide a custom API key. Options: "Use Credential API Key", "Use Custom API Key".
Custom API Key A string field to input a custom API key, used only if "Use Custom API Key" is selected in Operation Mode. Useful for multi-calendar scenarios.
Return All Data Boolean flag indicating whether to return the full response data from the API (true) or just the main event details (false).
Event ID The UUID of the event to retrieve. This is a required string identifying the specific calendar event.

Output

The node outputs JSON data representing the event details. Depending on the "Return All Data" property:

  • If Return All Data is true, the output contains the complete raw response from the API.
  • If Return All Data is false, the output includes a simplified object with the following fields:
    • event_id: The unique identifier of the event.
    • summary: The event title or summary.
    • description: Detailed description of the event.
    • start: Start time of the event.
    • end: End time of the event.
    • recurrenceRule: Recurrence rule if the event repeats.

The output is structured as an array of items, each with a json property containing the event data.

The node does not output binary data.

Dependencies

  • Requires an API key for authentication, which can be provided either via a configured credential or as a custom API key.
  • Needs network access to the RFCALENDAR API endpoint specified by the base URL in the credentials.
  • The node expects the credential to provide at least two pieces of information: the API key and the base URL of the RFCALENDAR service.

Troubleshooting

  • Invalid or missing API key: If the API key is incorrect or missing, the request will fail with an authorization error. Ensure that the correct API key is provided either through the credential or the custom API key field.
  • Incorrect Event ID: Providing an invalid or non-existent event UUID will result in an error or empty response. Verify the event ID before running the node.
  • Network issues: Failure to reach the RFCALENDAR API due to network problems or incorrect base URL configuration will cause errors. Check connectivity and credential settings.
  • Continue On Fail behavior: If enabled, the node will output error messages in the JSON output instead of stopping execution, allowing workflows to handle failures gracefully.

Links and References

Discussion