Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
The "Find Message Channel Duplicates" operation in the Message Channels resource is designed to identify duplicate message channels based on specified criteria. This node sends a request with filtering parameters and returns information about message channels that are considered duplicates according to the provided data and IDs.
This operation is useful in scenarios where you want to clean up or manage your messaging system by detecting redundant or overlapping message channels. For example, it can help in deduplicating email threads, chat channels, or other communication streams to maintain a tidy and efficient messaging environment.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information to include in the response: - 0: Only the primary message channel object. - 1: Primary object plus its directly related objects. - 2: Primary object, its related objects, and their related objects. |
| Data | JSON array specifying filter criteria for finding duplicates. This typically includes properties like synchronization stage, status, contact creation policy, type (e.g., email), and visibility. |
| Ids | JSON array of IDs to narrow down which message channels to check for duplicates. Can be used to specify particular message channel identifiers to focus the search. |
Output
The node outputs JSON data representing the found duplicate message channels. The structure corresponds to the API's response format, including the requested depth of nested related objects as specified by the Depth property.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the external Twenty API service.
- The node uses the base URL and headers configured via credentials.
- The operation relies on sending HTTP requests with query parameters and JSON bodies formatted according to the input properties.
Troubleshooting
- Invalid JSON in Data or Ids: Since
DataandIdsexpect JSON strings parsed into 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 or token is correctly set up.
- Incorrect Depth Values: Using unsupported depth values outside 0, 1, or 2 may lead to unexpected responses or errors.
- Empty or Null IDs: Providing null or empty IDs might return no results or unintended duplicates. Confirm that IDs are correctly specified if filtering by them.
- API Rate Limits or Network Issues: Standard network troubleshooting applies if requests fail due to connectivity or rate limiting.
Links and References
- Twenty API Documentation (Assumed official API docs for reference)
- n8n Documentation on HTTP Request Node for understanding request routing and body formatting.