TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation updates a single calendar event by its unique identifier. It allows users to modify various details of an existing event such as its title, timing, location, description, and conference links. This is useful in scenarios where event details change after creation and need to be kept up-to-date, for example, rescheduling meetings, updating meeting locations, or adding conference call information.

Practical examples:

  • Changing the start and end times of a scheduled meeting.
  • Adding or updating a video conference link for a remote event.
  • Marking an event as canceled or changing its description.

Properties

Name Meaning
Id The unique identifier of the calendar event to update.
Depth Level of nested related objects to include in the response: 0 (only primary object), 1 (primary + directly related objects), 2 (primary + directly related + their related objects).
Conference Link JSON object representing meeting links associated with the event, including secondary links.
Location Physical or virtual location of the event.
I Cal UID iCalendar unique identifier for the event.
Description Textual description or notes about the event.
External Updated At Timestamp indicating when the event was last updated externally.
External Created At Timestamp indicating when the event was created externally.
Ends At End date and time of the event.
Starts At Start date and time of the event.
Is Full Day Boolean flag indicating if the event lasts the entire day.
Is Canceled Boolean flag indicating if the event has been canceled.
Title Title or name of the event.
Conference Solution String specifying the conference solution used (e.g., Zoom, Google Meet).

Output

The node outputs a JSON object representing the updated calendar event. The structure includes all the fields that were sent for update along with any additional metadata returned by the API, depending on the depth parameter. This may include nested related objects such as attendees or reminders if requested.

If the node supports binary data output (not indicated here), it would typically represent attachments or related files, but this operation focuses on JSON event data only.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external calendar service.
  • The node uses a REST API endpoint to perform the update operation.
  • Proper configuration of base URL and headers is necessary, typically handled via credentials.

Troubleshooting

  • Missing or invalid Id: The update will fail if the event ID is not provided or incorrect. Ensure the correct event ID is supplied.
  • Invalid date formats: Start and end dates must be in a valid ISO 8601 string format; otherwise, the API may reject the request.
  • Permission errors: If the API key lacks permissions to update events, the node will return authorization errors.
  • Malformed JSON in Conference Link: The conferenceLink property expects valid JSON; invalid JSON will cause parsing errors.
  • Depth parameter misuse: Setting depth too high might result in large responses or slow performance; use appropriate depth level based on needs.

Links and References

  • Refer to the calendar service's official API documentation for detailed field definitions and constraints.
  • General best practices for managing calendar events via APIs can be found in common calendar API docs like Google Calendar API or Microsoft Graph API.

Discussion