TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

The "Find Note Target Duplicates" operation for the "Note Targets" resource is designed to identify duplicate note targets based on provided criteria. This node is useful in scenarios where you need to clean up or manage data by detecting repeated entries of note targets, which can help maintain data integrity and avoid redundancy.

For example, if you have a list of note targets and want to find duplicates before importing or processing them further, this operation will return those duplicates according to the specified parameters.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only the primary note target object.
- 1: The primary object plus its directly related objects (no further nesting).
- 2: The primary object, its related objects, and their related objects as well.
Data JSON array representing the data used to find duplicates. This typically contains the note target objects or criteria against which duplicates are searched.
Ids JSON array of IDs to be considered when finding duplicates. This can limit the search scope to specific note target IDs.

Output

The output json field contains the results of the duplicate search. It includes the note target objects identified as duplicates along with their related data depending on the selected depth level. The structure reflects the original note target data enriched with nested related objects as per the depth setting.

If binary data were involved, it would represent associated files or attachments linked to the note targets, 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 configured via credentials, including a domain URL and authentication headers.
  • No additional environment variables are explicitly required beyond standard API credential configuration.

Troubleshooting

  • Invalid JSON in Data or Ids: Since the data and ids properties expect JSON input, malformed JSON will cause errors. Ensure that these inputs are valid JSON arrays.
  • Authentication Errors: If the API key or domain is incorrect or missing, the node will fail to connect. Verify that the API credentials are correctly set up.
  • Depth Parameter Misuse: Setting an unsupported depth value outside 0, 1, or 2 may lead to unexpected responses or errors. Use only the provided options.
  • Empty Results: If no duplicates are found, the output will be empty. Confirm that the input data actually contains potential duplicates.

Links and References

Discussion