TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

This node interacts with the Twenty API to retrieve detailed information about a specific Calendar Channel Event Association by its unique identifier. It is useful when you need to fetch a single event association from a calendar channel, including optionally nested related objects depending on the depth level specified.

Practical examples include:

  • Retrieving details of a particular calendar event association for display or processing.
  • Fetching related objects such as linked events or channels up to two levels deep to understand relationships.
  • Integrating calendar event data into workflows that require precise event association information.

Properties

Name Meaning
Id The unique identifier of the Calendar Channel Event Association object to retrieve. This is required.
Depth Determines how much related nested data to include in the response:
- 0: Only the primary object's information.
- 1: Primary object plus directly related objects.
- 2: Primary object, directly related objects, and their related objects.

Output

The node outputs JSON data representing the requested Calendar Channel Event Association object. The structure includes the main object's properties and, depending on the Depth parameter, may also include nested related objects up to two levels deep.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Twenty API.
  • The base URL for the API is configured dynamically from the provided credentials.
  • The node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Missing or invalid Id: If the Id property is empty or incorrect, the API will likely return an error indicating the object was not found. Ensure the correct ID is provided.
  • Authentication errors: If the API key credential is missing or invalid, authentication failures will occur. Verify that the API key is correctly set up in n8n credentials.
  • Depth parameter misuse: Providing an unsupported depth value (other than 0, 1, or 2) might cause unexpected results or errors. Use only the allowed options.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful API calls. Check network access and credential domain settings.

Links and References

Discussion