TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

The node interacts with the "Tasks" resource of an external API to find duplicate tasks based on specified criteria. It allows users to specify filtering data and task IDs to narrow down the search for duplicates. The node supports controlling the depth of related objects included in the response, enabling users to retrieve just the primary task information or include nested related objects up to two levels deep.

This node is beneficial in scenarios where managing task duplication is critical, such as project management systems or task tracking applications. For example, it can be used to identify and merge duplicate tasks automatically or alert users about potential duplicates before creating new tasks.

Properties

Name Meaning
Depth Determines the level of nested related objects to include in the response:
- 0: Returns only the primary task's information.
- 1: Returns the primary task along with its directly related objects.
- 2: Returns the primary task, its directly related objects, and their related objects.
Data JSON object(s) specifying the criteria to find duplicate tasks. This typically includes fields like status or other task attributes to filter duplicates.
Ids JSON array of task IDs to limit the duplicate search to specific tasks. Can be null or contain multiple IDs.

Output

The node outputs a JSON structure containing the found duplicate tasks according to the specified criteria and depth. The output includes the primary task data and, depending on the depth setting, nested related objects. There is no indication that the node outputs binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the external "Twenty" API.
  • The base URL for the API is configured via credentials.
  • The node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Common issues:
    • Invalid JSON format in the "Data" or "Ids" properties may cause parsing errors.
    • Incorrect or missing API credentials will result in authentication failures.
    • Setting an unsupported depth value outside 0-2 may lead to unexpected responses or errors.
  • Error messages:
    • Authentication errors typically indicate invalid or missing API keys; verify credentials configuration.
    • JSON parsing errors suggest malformed input in the "Data" or "Ids" fields; ensure valid JSON syntax.
    • API response errors might occur if the requested resources do not exist or if the user lacks permissions.

Links and References

Discussion