Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Note → Create
AI-generatedOverview
This node operation creates a new note in the Didar CRM system. It allows users to add textual notes associated with various entities such as deals, cases, or contacts. This is useful for logging important information, updates, or comments related to CRM records.
Common scenarios include:
- Adding follow-up notes after client meetings.
- Logging internal comments on deals or cases.
- Tagging notes for categorization and easy retrieval.
For example, a sales representative can create a note summarizing a call with a client, assign tags for priority, link it to a specific deal, and set the responsible owner.
Properties
| Name | Meaning |
|---|---|
| Result Note | The text content of the note. Required. |
| Tags | List of Tag IDs (GUID). Accepts multiple entries via CSV, comma/semicolon, new lines, or JSON array (e.g. ["id1","id2"]). Sent only if "Result Note" is provided. |
| Owner Input Mode | Choose how to set the owner of this note: "Select from list" or "Enter ID manually". |
| Owner | Select the owner user from a loaded list of users (required if Owner Input Mode is "Select from list"). |
| Owner ID | Enter the owner user ID manually (required if Owner Input Mode is "Enter ID manually"). |
| Done Date | Completion date/time of the note. Defaults to current date/time if not provided. |
| Deal ID | Optional related deal ID (GUID) to associate the note with a deal. Default is an empty GUID. |
| Case ID | Optional related case ID (GUID) to associate the note with a case. Default is an empty GUID. |
| Contact IDs | List of related contact IDs (GUIDs). Optional. Accepts multiple values. |
Output
The node outputs an array of JSON objects representing the created note(s). Each output item contains the details of the newly created note, including its unique identifier, content, associated tags, owner, related entities (deal, case, contacts), and timestamps.
If binary data were involved (not in this case), it would be summarized accordingly, but this node handles only JSON data related to note creation.
Dependencies
- Requires an API key credential for authenticating with the Didar CRM API.
- The node depends on the Didar CRM service being accessible and properly configured.
- The "Owner" selection option loads available users dynamically via an API call.
- Proper permissions are needed to create notes and assign owners/tags within the CRM.
Troubleshooting
- Missing Required Fields: If "Result Note" or owner fields are missing, the node will likely throw validation errors. Ensure all required properties are filled.
- Invalid GUIDs: Providing malformed or invalid GUIDs for Deal ID, Case ID, or Contact IDs may cause API errors. Verify GUID formats.
- Owner Selection Issues: If using "Select from list" mode, ensure the user list loads correctly; network or permission issues might prevent loading users.
- API Authentication Errors: Invalid or expired API credentials will cause authentication failures. Check and update the API key credential.
- Date Format Problems: Incorrectly formatted "Done Date" values may lead to errors. Use the node's date/time picker or ISO 8601 format.
Links and References
- Didar CRM API Documentation (replace with actual URL)
- n8n Documentation - Creating Custom Nodes
- Working with Dates in n8n