TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Opportunity Duplicates, is designed to identify duplicate opportunity records based on provided data or IDs. It is useful in scenarios where you want to clean up your sales pipeline by detecting and handling duplicate opportunities that may have been entered multiple times. For example, a sales team can use this node to automatically find duplicates before creating new opportunities, ensuring data integrity and avoiding redundant follow-ups.

Properties

Name Meaning
Depth Determines how much related object information to include in the response:
- 0: Only the primary opportunity object.
- 1: Primary object plus its directly related objects.
- 2: Primary object, its related objects, and their related objects.
Data JSON array representing opportunity details to check for duplicates. Each object can include fields like stage, name, and amount (with subfields amountMicros and currencyCode).
Ids JSON array of opportunity IDs to check for duplicates. Can be used alternatively or alongside Data.

Output

The node outputs JSON data containing the results of the duplicate search. The structure includes the matched opportunity records along with related objects depending on the selected depth level. This output allows further processing or decision-making based on identified duplicates.

If binary data were involved, it would typically represent attachments or files related to the opportunities, but this node focuses on JSON data only.

Dependencies

  • Requires an API key credential to authenticate requests to the external service providing opportunity data.
  • The node uses a base URL configured via credentials to connect to the relevant API endpoint.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Invalid JSON in Data or Ids: Since Data and Ids expect JSON input, 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 or token is correctly configured.
  • Empty Results: If no duplicates are found, the output may be empty or minimal. Confirm that the input data or IDs are correct and exist in the system.
  • Depth Misconfiguration: Setting an unsupported depth value could lead to incomplete or unexpected data. Use only the allowed options (0, 1, or 2).

Links and References

  • JSON Format Guide — for preparing valid JSON inputs.
  • General API Authentication Best Practices — consult your API provider’s documentation for setting up credentials.
  • Duplicate Management Strategies in CRM Systems — for understanding practical applications of duplicate detection.

Discussion