TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Calendar Channel Event Association Duplicates, is designed to identify duplicate associations within calendar channel events. It helps users detect overlapping or repeated event links in their calendar channels, which can be useful for cleaning up data, avoiding redundant notifications, or ensuring data integrity in calendar management workflows.

Typical use cases include:

  • Synchronizing calendar data from multiple sources and removing duplicates.
  • Auditing calendar event associations to maintain clean records.
  • Automating calendar maintenance tasks by flagging or handling duplicate entries.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only the primary object's information.
- 1: Primary object plus directly related objects (no further nesting).
- 2: Primary object, its related objects, and their related objects.
Data JSON array representing the data payload to search for duplicates. This typically contains the event association details to be checked.
Ids JSON array of IDs to filter or specify particular calendar channel event associations to consider when finding duplicates.

Output

The output is a JSON structure containing the found duplicate calendar channel event associations according to the input criteria. The exact structure depends on the API response but generally includes:

  • Details of each duplicate association found.
  • Nested related objects depending on the Depth parameter.
  • Metadata about the duplicates such as counts or identifiers.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the external Twenty API service.
  • The node uses the Twenty API base URL configured via credentials.
  • The operation sends HTTP requests with JSON bodies and expects JSON responses.

Troubleshooting

  • Invalid JSON in Data or Ids: Since these properties expect JSON arrays, malformed JSON will cause errors. Ensure valid JSON syntax.
  • Authentication Errors: Missing or incorrect API credentials will result in authorization failures.
  • Depth Parameter Misuse: Using unsupported depth values may lead to unexpected results or errors; only 0, 1, or 2 are valid.
  • Empty or Incorrect Data: Providing empty or irrelevant data arrays might return no duplicates or error responses.
  • API Rate Limits: Excessive requests could trigger rate limiting; handle retries or backoff accordingly.

Links and References

Discussion