TwentyDEV icon

TwentyDEV

Consume the Twenty API

Actions252

Overview

The "Find Message Duplicates" operation in the Messages resource is designed to identify duplicate messages based on provided criteria. This node is useful when you want to detect repeated or redundant messages within a dataset, which can help in cleaning data, avoiding processing duplicates, or managing message integrity.

Practical examples include:

  • Detecting duplicate chat messages in a messaging app.
  • Identifying repeated notifications or alerts in a system.
  • Filtering out duplicate entries before further processing or analysis.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only the primary message object.
- 1: Primary message plus directly related objects.
- 2: Primary message, its related objects, and their related objects.
Data JSON array representing the message data to be checked for duplicates. The structure depends on the API's expected message format.
Ids JSON array of message IDs to check for duplicates. Can be used alternatively or alongside Data to specify which messages to analyze.

Output

The node outputs JSON data containing the results of the duplicate search. The exact structure depends on the API response but generally includes information about the identified duplicate messages and their related objects according to the specified depth.

If binary data were involved (e.g., attachments), it would be summarized here, but this operation focuses on JSON message data only.

Dependencies

  • Requires an API key credential to authenticate requests to the Twenty API service.
  • The node uses the Twenty API base URL configured via credentials.
  • No additional external dependencies are indicated.

Troubleshooting

  • Invalid JSON in Data or Ids: Since data and ids properties expect JSON input, malformed JSON will cause errors. Ensure valid JSON formatting.
  • Authentication Errors: Missing or incorrect API credentials will result in authentication failures. Verify that the API key and domain are correctly set in the node credentials.
  • Depth Parameter Misuse: Using unsupported depth values may lead to unexpected responses or errors. Use only 0, 1, or 2 as defined.
  • Empty or Missing Input: Providing empty arrays or null values for data or ids might return no results or errors. Ensure meaningful input is provided.

Links and References

Discussion