TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Connected Account Duplicates, is designed to identify duplicate connected accounts within a system by sending specific data and optional filters to an external API. It allows users to specify the depth of related objects to include in the response, enabling flexible retrieval of nested information about duplicates. This can be particularly useful for data cleanup, synchronization tasks, or ensuring data integrity by detecting and handling duplicate account entries.

Practical examples:

  • A marketing team wants to find duplicate social media accounts connected to their CRM to avoid sending multiple campaigns to the same user.
  • An IT administrator needs to audit connected service accounts across platforms to merge or remove duplicates.
  • A developer automates the process of identifying duplicate OAuth connections in an application to streamline user management.

Properties

Name Meaning
Depth Determines how much related object data to include in the response:
- 0: Only the primary connected account information.
- 1: Primary object plus directly related objects (no further nesting).
- 2: Primary object, its related objects, and those related objects' related objects.
Data JSON array containing the data used to find duplicates. This typically includes the connected account details or criteria against which duplicates are searched.
Ids JSON array of IDs to filter or specify particular connected accounts to check for duplicates. Can be used to limit the scope of the duplicate search.

Output

The node outputs JSON data representing the found duplicate connected accounts according to the specified depth and input criteria. The structure includes the primary connected account objects and, depending on the depth, their related nested objects. This output can be used downstream for further processing, reporting, or automated actions like merging duplicates.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential to authenticate requests to the external Twenty API service.
  • The node uses the base URL and headers configured via credentials, including JSON content type and accept headers.
  • No additional environment variables or configurations are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid JSON format in the "Data" or "Ids" properties can cause request failures. Ensure valid JSON syntax.
    • Incorrect or missing API credentials will result in authentication errors.
    • Setting an unsupported depth value outside 0, 1, or 2 may lead to unexpected responses or errors.

  • Error messages:

    • Authentication errors typically indicate invalid or missing API keys; verify credentials.
    • JSON parsing errors suggest malformed input in the "Data" or "Ids" fields; validate JSON before execution.
    • API response errors might occur if the requested resource or operation is not supported; confirm correct usage of the node's properties.

Links and References

  • Twenty API Documentation — Official documentation for the Twenty API, detailing endpoints and data structures.
  • n8n Documentation — General guidance on creating and using custom nodes and managing credentials.

Discussion