TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

The "Find Task Target Duplicates" operation in the Task Targets resource is designed to identify duplicate task targets based on provided criteria. This node sends data and optional identifiers to an API endpoint, which then returns information about duplicates found among task targets. It supports controlling the depth of related nested objects included in the response, allowing users to tailor the detail level of returned data.

This node is beneficial when managing tasks that may have overlapping or redundant targets, helping to clean up or consolidate task assignments. For example, a project manager could use this node to detect if multiple tasks are targeting the same user or resource unintentionally.

Properties

Name Meaning
Depth Determines how much related nested object information to include in the response:
- 0: Only primary task target information.
- 1: Primary task target plus directly related objects.
- 2: Primary, directly related, and their related objects.
Data JSON array containing the data used to find duplicates. This typically includes the task target details to be checked for duplication.
Ids JSON array of IDs corresponding to task targets to consider in the duplicate search. Can be null or empty if not filtering by specific IDs.

Output

The node outputs JSON data representing the found duplicate task targets. The structure reflects the requested depth of nested related objects, providing detailed information about each duplicate and its relationships depending on the depth setting.

No binary data output is indicated.

Dependencies

  • Requires an API key credential to authenticate requests to the Twenty API.
  • The base URL for the API is configured via credentials.
  • The node uses the Twenty API's OpenAPI specification version 1.0.3 for request construction.

Troubleshooting

  • Invalid JSON in Data or Ids: Since data and ids properties expect JSON input, malformed JSON will cause errors. Ensure valid JSON formatting.
  • Authentication Errors: Missing or incorrect API credentials will result in authentication failures. Verify that the API key credential is correctly set up.
  • Depth Parameter Misuse: Providing a depth value outside the allowed range (0, 1, 2) may cause unexpected results or errors. Use only the specified options.
  • Empty Results: If no duplicates are found, the output JSON may be empty or minimal. Confirm that the input data actually contains potential duplicates.

Links and References

Discussion