Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node operation, Find One Calendar Event, retrieves detailed information about a single calendar event by its unique identifier. It is useful when you need to fetch specific event details from a calendar system, such as for displaying event information, updating UI elements, or processing event data in workflows.
Common scenarios include:
- Fetching an event's full details before editing or updating it.
- Displaying event information in a dashboard or notification.
- Integrating with other systems that require event metadata.
For example, you might use this node to get the start time, attendees, and description of a meeting event by providing its ID.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the calendar event to retrieve. This is required to specify which event to find. |
| Depth | Determines how much related nested data to include in the response: - 0: Only the primary event object.- 1: The event plus directly related objects (e.g., attendees).- 2: The event, its related objects, and their related objects. |
Output
The node outputs a JSON object representing the calendar event specified by the given ID. The structure includes the event's core properties such as title, start and end times, location, description, and potentially nested related objects depending on the Depth parameter.
If Depth is set higher, the output will include nested related entities like attendees, reminders, or linked resources, up to two levels deep.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate requests against the Twenty API service.
- The node uses the base URL configured in the credentials to send HTTP requests.
- No additional external dependencies are needed beyond the provided API access.
Troubleshooting
- Missing or invalid Id: If the
Idproperty is empty or incorrect, the node will fail to find the event. Ensure the correct event ID is provided. - Authentication errors: If the API key or domain credentials are misconfigured, the request will be unauthorized. Verify credentials in n8n settings.
- Depth parameter misuse: Setting an unsupported depth value may cause unexpected results or errors. Use only 0, 1, or 2 as allowed.
- Event not found: If the event ID does not exist, the API will return an error or empty result. Confirm the event exists in the calendar system.
Links and References
- Twenty API Documentation (for general API reference)
- n8n documentation on creating custom nodes