TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation allows you to create a new calendar event in an external calendar system via the Twenty API. It is useful for automating event scheduling, integrating calendar data into workflows, or syncing events from other applications. For example, you could use this node to automatically add meetings, appointments, or reminders to your calendar when triggered by other workflow events.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response: 0 (only primary event), 1 (primary event + directly related objects), or 2 (primary event + related objects + their related objects).
Conference Link JSON object specifying meeting links associated with the event, such as video conference URLs.
Location The physical or virtual location of the event.
I Cal UID Unique identifier for the event in iCalendar format.
Description Text 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 is 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 newly created calendar event. The structure includes all the properties sent during creation along with any additional metadata returned by the API, respecting the specified depth level for nested related objects. If the event includes conference links or attachments, these will be included in the output JSON. The node does not output binary data.

Dependencies

  • Requires an active connection to the Twenty API service.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for the API is set dynamically from the credential domain.
  • The node sends requests with Content-Type: application/json and expects JSON responses.

Troubleshooting

  • Invalid or missing authentication: Ensure that the API key or token is correctly configured in the node credentials.
  • Incorrect date/time formats: The startsAt and endsAt fields must be valid ISO 8601 date-time strings; otherwise, the API may reject the request.
  • Required fields missing: The API might require certain fields like title or startsAt; verify these are provided.
  • API rate limits or connectivity issues: Network problems or hitting API limits can cause errors; check network access and API usage quotas.
  • Malformed JSON in Conference Link: The conferenceLink property expects valid JSON; invalid JSON syntax will cause failures.

Links and References

Discussion