TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Message Participant Duplicates, is designed to identify duplicate message participants within a dataset. It allows users to specify criteria and depth of related data to include in the response, helping to detect redundant or repeated participant entries in messaging contexts. This can be particularly useful for cleaning up contact lists, ensuring data integrity in communication platforms, or preparing datasets for analysis by removing duplicates.

Practical examples:

  • In a customer support system, find duplicate participants who have been mistakenly entered multiple times.
  • In a messaging app backend, identify and merge duplicate user entries to maintain consistent participant records.
  • During data migration, verify that no duplicate message participants exist before importing data into a new system.

Properties

Name Meaning
Depth Determines how much nested related information to include in the response:
- 0: Only the primary message participant object.
- 1: Primary object plus directly related objects (no further nesting).
- 2: Primary object, its related objects, and their related objects.
Data JSON array specifying criteria or filters for finding duplicates. For example, it might include roles like "from" to filter participants by their role in messages.
Ids JSON array of IDs to limit the search to specific message participants. Can be used to target particular entries when searching for duplicates.

Output

The node outputs JSON data representing the found duplicate message participants according to the specified criteria and depth. The structure includes the primary participant objects and, depending on the depth setting, their related nested objects. This output enables downstream nodes or workflows to process or act upon identified 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 Twenty API base URL configured via credentials.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Malformed JSON input in the Data or Ids properties may lead to request errors.
    • Setting an unsupported depth value outside 0, 1, or 2 could result in unexpected responses or errors.

  • Error messages:

    • Authentication errors typically indicate invalid or missing API keys; verify credential configuration.
    • JSON parsing errors suggest invalid JSON syntax in input fields; ensure proper formatting.
    • API response errors may occur if the requested resource or operation is not supported; confirm correct resource and operation selection.

Links and References

Discussion