TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Person Duplicates under the People resource, is designed to identify duplicate person records based on provided data or IDs. It helps users detect and manage duplicate entries in their contact or CRM systems by comparing key personal information such as names, phone numbers, emails, and links.

Common scenarios where this node is beneficial include:

  • Cleaning up contact lists by merging or removing duplicate person entries.
  • Ensuring data integrity in customer databases.
  • Automating duplicate detection workflows in sales or marketing pipelines.

For example, a user can input a list of people with their names, phone numbers, emails, and social links, and the node will return potential duplicates for review or further processing.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only primary person information.
- 1: Primary person plus directly related objects.
- 2: Primary person, directly related objects, and their related objects.
Data JSON array of person objects to check for duplicates. Each object can include fields like name (first and last), phones, emails, and links. This is the main input for finding duplicates based on detailed person data.
Ids JSON array of person record IDs to check for duplicates. Instead of full person data, you can provide existing record identifiers to find duplicates among them.

Output

The node outputs JSON data containing the results of the duplicate search. The structure typically includes matched person records flagged as duplicates along with their related information depending on the selected depth level.

If binary data were involved (e.g., profile pictures), it would be summarized here, but this node focuses on JSON data representing person entities and their relationships.

Dependencies

  • Requires an API key credential for authenticating requests to the external Twenty API service.
  • The node uses the Twenty API endpoint configured via credentials, which must include a valid domain and authentication token.
  • No additional environment variables are explicitly required beyond standard API credential setup.

Troubleshooting

  • Invalid JSON Input: If the Data or Ids properties contain malformed JSON, the node will fail to parse the input. Ensure JSON syntax is correct.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key/token is correctly configured in n8n credentials.
  • Empty Results: If no duplicates are found, the output may be empty or minimal. Confirm that the input data actually contains potential duplicates.
  • Depth Misconfiguration: Setting an unsupported depth value outside 0, 1, or 2 may lead to unexpected responses or errors. Use only the provided options.

Links and References

Discussion