Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
The node updates an existing note in the Didar CRM system by its unique identifier. It allows modifying the note's text content, associated tags, ownership, completion date, and related entities such as deals, cases, and contacts.
This node is useful when you need to programmatically maintain or correct notes linked to your CRM records, for example:
- Updating a customer interaction note with new information.
- Changing the owner of a note after reassignment.
- Adding tags to categorize notes for better filtering.
- Linking notes to specific deals or cases dynamically.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the note to update. |
| Result Note | The main text content of the note. This field is required and represents the updated note text. |
| Tags | List of tag IDs (GUIDs) to associate with the note. Accepts multiple entries via CSV, semicolon, new lines, or JSON array format. Sent only if "Result Note" is provided. |
| Owner Input Mode | How to specify the owner of the note: either select from a list of users or enter the owner ID manually. |
| Owner | When selecting from list mode, choose the owner user from available options. |
| Owner ID | When manual mode is selected, enter the owner user ID directly. |
| Done Date | Completion date/time of the note. If not provided, defaults to the current date/time. |
| Deal ID | Optional GUID of a related deal to link the note to. Defaults to a zero GUID if not specified. |
| Case ID | Optional GUID of a related case to link the note to. Defaults to a zero GUID if not specified. |
| Contact IDs | Optional list of related contact IDs (GUIDs). Accepts multiple values. |
Output
The node outputs an array of JSON objects representing the updated note(s). Each output item contains the updated note data as returned by the Didar CRM API, including fields such as the note ID, text content, tags, owner information, completion date, and linked entities.
If the node supports binary data output (not indicated here), it would typically represent attachments or media related to the note, but this node focuses on JSON data.
Dependencies
- Requires connection to Didar CRM via an API key credential configured in n8n.
- Uses Didar CRM API endpoints to perform note update operations.
- The node depends on internal methods to load user options for owner selection.
Troubleshooting
- Missing Required Fields: Errors may occur if "Note ID" or "Result Note" are not provided. Ensure these required properties are set.
- Invalid GUID Format: Related entity IDs (Deal ID, Case ID, Contact IDs, Tags) must be valid GUIDs. Invalid formats can cause API errors.
- Owner Selection Issues: If "Owner Input Mode" is set to select but no owner is chosen, or manual mode is used with an invalid owner ID, the update will fail.
- API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions to update notes.
- Network or API Errors: Temporary connectivity issues or API downtime can cause failures; retrying later or checking API status may help.
Links and References
- Didar CRM API Documentation (replace with actual URL)
- n8n Documentation - Creating Custom Nodes
- Working with GUIDs