Overview
This node updates an existing calendar event in the RFCALENDAR system. It allows users to modify various event details such as the title (summary), description, start and end times, location, timezone, attendees, and recurrence settings. The node supports flexible API key usage either from stored credentials or a custom key, making it suitable for multi-calendar scenarios.
Common use cases include:
- Changing the time or details of a scheduled meeting.
- Updating event descriptions or adding attendees dynamically.
- Adjusting recurring event patterns or removing recurrence.
- Managing events across multiple calendars with different API keys.
For example, you could automate updating a team meeting's time and attendees after receiving new scheduling information, or remove recurrence from a previously repeating event.
Properties
| Name | Meaning |
|---|---|
| Operation Mode | Choose whether to use the API key from the saved credential or provide a custom API key (useful for multi-calendar access). Options: "Use Credential API Key", "Use Custom API Key". |
| Custom API Key | A string field to input a custom API key when "Use Custom API Key" mode is selected. |
| Return All Data | Boolean flag to decide if the node should return the entire response data from the API or just the main event data. |
| Event ID | The UUID of the event to update. This is required to identify which event will be modified. |
| Update Summary/Title | Boolean flag indicating whether to update the event's title/summary. |
| Summary | The new title/summary text for the event. Shown only if "Update Summary/Title" is true. |
| Update Description | Boolean flag indicating whether to update the event's description. |
| Description | The new description text for the event. Shown only if "Update Description" is true. |
| Update Start Time | Boolean flag indicating whether to update the event's start date and time. |
| Start DateTime | The updated start date and time of the event. Shown only if "Update Start Time" is true. |
| Update End Time | Boolean flag indicating whether to update the event's end date and time. |
| End DateTime | The updated end date and time of the event. Shown only if "Update End Time" is true. |
| Additional Fields | Collection of optional fields: - Location: Physical location of the event. - Timezone: Timezone string (e.g., America/Sao_Paulo). - Attendees: Comma-separated list of attendee email addresses. |
| Update Recurrence | Boolean flag indicating whether to update the recurrence settings of the event. |
| Use Recurrence Rule | Boolean flag to specify if the event should repeat according to a recurrence rule. Set false to remove existing recurrence. Shown only if "Update Recurrence" is true. |
| Recurrence Rule (JSON) | JSON object defining the recurrence pattern with fields: - frequency: daily, weekly, monthly, yearly - intervalCount: number of intervals between recurrences - daysOfWeek: array of weekdays (for weekly) - dayOfMonth: day number (1-31 for monthly) - monthOfYear: month number (1-12 for yearly) - count: total occurrences - untilDate: ISO date string to end recurrence |
Output
The node outputs JSON data representing the result of the update operation for each input item. By default, it returns a simplified object containing:
event_id: The unique identifier of the updated event.success: A boolean indicating the update was successful.
If "Return All Data" is enabled, the node returns the full response from the API, which may include additional metadata about the event.
No binary data output is produced by this node.
Dependencies
- Requires an API key for authentication, either provided via stored credentials or a custom key.
- Needs network access to the RFCALENDAR API endpoint specified in the credentials.
- The node expects the API base URL and key to be configured properly in the credentials or passed explicitly.
Troubleshooting
- Invalid Recurrence Rule JSON: If the recurrence rule JSON is malformed or invalid, the node throws an error indicating the JSON parsing issue. Ensure the JSON syntax is correct and all required fields are valid.
- Missing or Invalid Event ID: The event ID must be provided and valid; otherwise, the API call will fail. Verify the event UUID before running the node.
- Authentication Errors: Using an incorrect or expired API key will cause authorization failures. Confirm that the API key is valid and has necessary permissions.
- Empty Attendees List Handling: If the attendees field is empty or improperly formatted, it may result in unexpected behavior. Provide a comma-separated list without extra spaces or empty entries.
- Network or API Endpoint Issues: Connectivity problems or incorrect base URL configuration can cause request failures. Check network access and credential settings.
Using the "Continue On Fail" option can help process multiple items even if some fail.
Links and References
- RFCALENDAR API Documentation (Replace with actual link if available)
- Recurrence Rule Specification (for understanding recurrence rules)