TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

The "Find Calendar Event Duplicates" operation in the Calendar Events resource is designed to identify duplicate calendar events based on provided data and IDs. This node is useful when you want to clean up or manage your calendar by detecting repeated or overlapping events, which can help maintain an organized schedule and avoid confusion.

Practical examples include:

  • Automatically scanning newly imported calendar events to find duplicates before adding them.
  • Periodically checking existing calendar events for duplicates to prompt cleanup.
  • Integrating with other workflows that require deduplication of event data.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only the primary event's information.
- 1: Primary event plus directly related objects (no further nesting).
- 2: Primary event, its related objects, and their related objects.
Data JSON array representing the calendar event data to check for duplicates. This should contain the event details such as conference links or other relevant fields used to identify duplicates.
Ids JSON array of event IDs to consider when searching for duplicates. This helps narrow down the search scope to specific events.

Output

The node outputs a JSON structure containing the found duplicate calendar events according to the specified depth level. The output includes the primary event data and, depending on the depth setting, related nested objects. This allows downstream nodes or processes to handle duplicates appropriately, such as merging, deleting, or notifying users.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential to authenticate requests to the external calendar service.
  • The node uses a base URL configured via credentials to connect to the calendar API.
  • The operation depends on the external calendar system's API supporting duplicate detection endpoints.

Troubleshooting

  • Invalid JSON in Data or Ids: Since data and ids are expected as JSON strings parsed into arrays, malformed JSON will cause errors. Ensure valid JSON formatting.
  • Authentication Errors: Missing or incorrect API credentials will prevent successful API calls. Verify that the API key or token is correctly set up in n8n credentials.
  • Empty or Incorrect Input: Providing empty arrays or irrelevant event data may result in no duplicates found or unexpected results. Double-check input values.
  • API Limitations: If the external calendar API has rate limits or restrictions, repeated calls might fail or be throttled.

Links and References

  • Refer to the external calendar service API documentation for details on duplicate detection endpoints and data formats.
  • n8n documentation on using JSON parameters and handling API credentials.

Discussion