TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Favorite Folder Duplicates, is designed to identify duplicate favorite folders based on specified criteria. It allows users to submit data representing favorite folders and returns information about duplicates found according to the input parameters.

Common scenarios where this node would be beneficial include:

  • Cleaning up a user's favorite folders by detecting and managing duplicates.
  • Synchronizing or merging folder structures where duplicates might cause conflicts.
  • Auditing folder collections to maintain organization and avoid redundancy.

For example, a user could provide a list of favorite folder names and request the node to find any duplicates among them, optionally including related nested objects up to a certain depth.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only the primary favorite folder object.
- 1: The primary object plus its directly related objects (no further nesting).
- 2: The primary object, its directly related objects, and their related objects.
Data JSON array describing the favorite folder data to check for duplicates. Typically includes folder attributes such as the folder name. Example: [{"name": "Favorite Folder name"}].
Ids JSON array of folder IDs to consider when finding duplicates. Can be used to limit the search scope to specific folders. Example: [null] if no specific IDs are provided.

Output

The output is a JSON object containing information about the detected duplicate favorite folders. The structure reflects the requested depth level, including nested related objects if applicable.

  • The json field contains the duplicate folder data matching the input criteria.
  • If the node supports binary data output (not indicated here), it would typically represent associated files or media linked to the folders, but this node 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, with base URL and headers preset for JSON communication.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Invalid JSON Input: Since Data and Ids properties expect JSON strings, malformed JSON will cause errors. Ensure valid JSON formatting.
  • Authentication Errors: Missing or incorrect API credentials will result in authorization failures. Verify that the API key credential is correctly configured.
  • Empty or Null Inputs: Providing empty arrays or null values may lead to no results or unexpected behavior. Confirm that meaningful data is supplied.
  • Depth Misconfiguration: Setting an unsupported depth value outside 0, 1, or 2 may cause the API to reject the request or return incomplete data.

Links and References

Discussion