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 Note Duplicates" operation in the Notes resource is designed to identify duplicate notes based on provided data or note IDs. This node is useful when you want to detect and handle duplicate content within a collection of notes, such as cleaning up redundant entries or merging duplicates. For example, it can be used in workflows that manage knowledge bases, customer support tickets, or any system where notes are frequently created and duplicates need to be identified automatically.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related information is included in the response: - 0: Only the primary note's information. - 1: The primary note plus its directly related objects. - 2: The primary note, its related objects, and their related objects. |
| Data | JSON array representing the note data to check for duplicates. This should contain the note objects or relevant fields to be analyzed. |
| Ids | JSON array of note IDs to check for duplicates. This allows specifying existing notes by their identifiers to find duplicates among them. |
Output
The output will be a JSON object containing the results of the duplicate search. It typically includes information about which notes are considered duplicates, possibly grouped or linked together. The exact structure depends on the API response but generally provides details sufficient to identify and process duplicate notes.
No binary data output is expected from 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.
- The node sends HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
- Invalid JSON in Data or Ids properties: Since these inputs expect JSON arrays, malformed JSON will cause errors. Ensure the JSON syntax is correct.
- Authentication errors: If the API key or domain is not set correctly in credentials, the node will fail to connect.
- Empty or missing input data: Providing empty arrays or null values may result in no duplicates found or errors. Make sure to supply valid note data or IDs.
- Depth parameter misuse: Setting depth too high might increase response size and processing time unnecessarily.
Links and References
- Twenty API Documentation (general reference for the underlying API)
- n8n documentation on working with JSON parameters