RFCALENDAR: Check Availability

Check calendar availability within a specified time range in RFCALENDAR

Overview

This node checks calendar availability within a specified time range using the RFCALENDAR service. It is useful for determining if a particular time slot is free for scheduling events or meetings. Common scenarios include booking appointments, coordinating meetings across multiple calendars, or verifying open time slots before creating new calendar entries.

For example, you can use this node to:

  • Verify if a meeting room or resource is available between two dates.
  • Check user availability before sending out meeting invites.
  • Integrate with other workflow steps that require confirmation of free time slots.

Properties

Name Meaning
Operation Mode Choose whether to use the API key from the stored credential or provide a custom API key. Options: "Use Credential API Key", "Use Custom API Key"
Custom API Key A custom API key string used when "Use Custom API Key" mode is selected. Useful for multi-calendar scenarios.
Return All Data Boolean flag indicating whether to return the full response data from the API or just the main availability information.
Start DateTime The start date and time for the availability check (required).
End DateTime The end date and time for the availability check (required).

Output

The node outputs JSON data representing the availability status for the specified time range.

  • If Return All Data is set to false (default), the output JSON contains:

    • available: A boolean indicating if the time slot is available.
    • conflicts: An array listing any conflicting events or bookings during the time slot (empty if none).

  • If Return All Data is set to true, the entire API response is returned as-is, which may include additional metadata beyond availability and conflicts.

Example output when returning main data only:

{
  "available": true,
  "conflicts": []
}

Dependencies

  • Requires an API key for authentication, either provided via stored credentials or as a custom API key input.
  • Needs access to the RFCALENDAR API endpoint, configured by the base URL in the credentials.
  • The node performs HTTP GET requests to the /api/availability endpoint of the RFCALENDAR service.

Troubleshooting

  • Invalid API Key or Authentication Errors: Ensure the API key is correct and has proper permissions. Use the credential-based API key or verify the custom API key input.
  • Missing Required Parameters: Both start and end date/time must be provided; otherwise, the request will fail.
  • Network or Endpoint Issues: Confirm the base URL in credentials is reachable and the RFCALENDAR service is operational.
  • Error Handling: If the node encounters an error and "Continue On Fail" is enabled, it returns an error message in the output JSON instead of stopping the workflow.

Links and References

Discussion