RFCALENDAR: Create Event

Create a calendar event in RFCALENDAR

Overview

This node creates calendar events in the RFCALENDAR service. It allows users to specify event details such as title, description, start and end times, location, attendees, and timezone. Additionally, it supports creating recurring events by defining recurrence rules in JSON format.

Common scenarios for this node include:

  • Automating event creation from form submissions or CRM data.
  • Scheduling meetings with multiple attendees automatically.
  • Creating recurring reminders or appointments on a calendar.
  • Integrating custom applications with RFCALENDAR to manage events programmatically.

For example, you could use this node to create a daily standup meeting event every weekday with a predefined list of attendees and a specific timezone.

Properties

Name Meaning
Operation Mode Choose whether to use the API key stored in the node's credential or provide a custom API key directly (useful for multi-calendar scenarios).
Custom API Key A string field to input a custom API key if "Use Custom API Key" mode is selected.
Return All Data Boolean flag to decide whether to return the full response from the API or just the main event ID and success status.
Summary The title or summary of the calendar event. This is a required field.
Description A textual description of the event. Optional.
Start DateTime The starting date and time of the event. Required.
End DateTime The ending date and time of the event. Required.
Additional Fields A collection of optional fields:
- Location: Physical location of the event.
- Timezone: Timezone identifier for the event (default is America/Sao_Paulo).
- Attendees: Comma-separated emails of attendees.
Use Recurrence Rule Boolean flag indicating if the event should be recurring.
Recurrence Rule (JSON) JSON object defining recurrence parameters such as frequency (daily, weekly, monthly, yearly), interval count, days of week, day of month, month of year, number of occurrences, and until date. Shown only if recurrence is enabled.

Output

The node outputs an array of JSON objects, one per input item processed. Each output JSON contains either:

  • If Return All Data is false (default): 

    {
  "event_id": "<string>",
  "success": true
}

    where event_id is the unique identifier of the created event.

  • If Return All Data is true:
    The full JSON response returned by the RFCALENDAR API for the created event.

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for RFCALENDAR or a custom API key provided in the node parameters.
  • The node makes HTTP POST requests to the RFCALENDAR API endpoint /api/events.
  • The base URL for the API is obtained from the credential configuration.
  • Proper network access to the RFCALENDAR API endpoint is necessary.

Troubleshooting

  • Invalid recurrence rule JSON:
    If the recurrence rule JSON is malformed or invalid, the node throws an error like:
    Invalid recurrence rule JSON: <error message>
    To fix, ensure the JSON syntax is correct and all fields conform to expected types and values.

  • Authentication errors:
    If the API key is missing, invalid, or unauthorized, the API will reject the request. Verify that the API key is correctly set either in credentials or as a custom key.

  • Missing required fields:
    The node requires summary, startDateTime, and endDateTime. Omitting these will cause errors or failed event creation.

  • Network or API errors:
    Any HTTP errors from the API will be thrown unless "Continue On Fail" is enabled, in which case the error message will be included in the output JSON under error.

Links and References

Discussion