TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Calendar Event Participant Duplicates, is designed to identify duplicate participants within calendar events. It helps users detect and manage repeated entries of participants in event data, which can be useful for cleaning up event records or ensuring participant lists are accurate.

Common scenarios include:

  • Synchronizing calendar data where duplicates might have been introduced.
  • Preparing participant lists for notifications or reporting without redundancies.
  • Auditing event data integrity by finding repeated participant entries.

For example, if a calendar event has multiple entries for the same participant due to syncing issues, this operation will find those duplicates based on specified criteria.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only the primary participant object.
- 1: Primary object plus directly related objects.
- 2: Primary object, its related objects, and their related objects.
Data JSON array specifying filters or conditions to apply when searching for duplicates. For example, filtering participants by response status like "NEEDS_ACTION".
Ids JSON array of participant IDs to limit the search scope to specific participants. Can contain null values if no specific IDs are provided.

Output

The output is a JSON structure containing the found duplicate calendar event participants according to the input criteria. The exact structure depends on the API response but generally includes participant details and possibly nested related objects depending on the Depth parameter.

If binary data were involved (not indicated here), it would typically represent attachments or files related to participants, but this operation focuses on JSON data only.

Dependencies

  • Requires an API key credential to authenticate requests to the external Twenty API service.
  • The node uses the Twenty API's endpoint for calendar event participants.
  • Proper configuration of the API base URL and authentication credentials in n8n is necessary.

Troubleshooting

  • Invalid JSON in Data or Ids properties: Since these fields expect JSON arrays, malformed JSON will cause errors. Ensure valid JSON syntax.
  • Authentication errors: If the API key or domain is misconfigured, the node will fail to connect. Verify credentials and base URL.
  • No duplicates found: This may indicate that the filter criteria are too restrictive or that there truly are no duplicates. Adjust the Data filter or check the participant list.
  • Unexpected response structure: If the Depth parameter is set incorrectly, the returned data may not include expected nested objects. Try adjusting the depth level.

Links and References

Discussion