TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Company Duplicates, is designed to identify duplicate company records based on provided data or IDs. It helps users detect and manage redundant company entries in their datasets or CRM systems. This can be particularly useful for data cleansing, deduplication workflows, or ensuring data integrity before further processing.

Typical use cases include:

  • Cleaning up company databases by finding duplicates before importing new data.
  • Automating the detection of duplicate companies during data synchronization processes.
  • Enhancing CRM data quality by identifying potential duplicate company profiles.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only the primary company object.
- 1: Primary object plus directly related objects.
- 2: Primary object, its related objects, and their related objects.
Data JSON array of company objects to check for duplicates. Each object can include fields like company name, domain name URLs, LinkedIn links, other links, and financial info such as annual recurring revenue.
Ids JSON array of company IDs to check for duplicates. Can be used alternatively or alongside the Data property to specify which companies to analyze.

Output

The node outputs JSON data representing the found duplicate companies according to the input criteria. The structure includes the primary company objects along with related nested objects depending on the selected depth level. The output provides detailed information about each duplicate group detected.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the external Twenty API service.
  • The node uses the Twenty API base URL configured via credentials.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Invalid JSON in Data or Ids: Since these properties expect JSON arrays, 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.
  • Depth Parameter Misuse: Using a depth value outside the allowed range (0, 1, 2) may cause unexpected results or errors.
  • Empty Input Arrays: Providing empty arrays for both Data and Ids might lead to no results or errors. Make sure at least one contains valid entries.

Links and References

Discussion