Actions46
- Company Actions
- Note Actions
- Note Relation Actions
- Opportunity Actions
- Person Actions
- Pipeline Actions
- Task Actions
- Task Relation Actions
Note → Update
AI-generatedOverview
This node updates an existing note in the Dalil AI system. It allows users to modify the note's title, body content (in plain text or markdown), and other optional fields such as position, visibility level, group ID, and the source of creation. The node supports specifying the depth of nested related objects to include in the response, enabling retrieval of related data along with the updated note. This operation is useful for scenarios where notes need to be edited or enriched with additional information after creation, such as updating meeting notes, project updates, or call summaries.
Use Case Examples
- Updating the title and body of a note to reflect new information from a recent meeting.
- Changing the visibility level of a note to restrict or expand access.
- Adding or modifying the group ID associated with a note for better organization.
Properties
| Name | Meaning |
|---|---|
| Note Title or Name or ID | UUID string of the note to update. Choose from the list, or specify an ID using an expression. |
| Update Fields | Fields to update on the note, including title and body content in markdown format. |
| Depth Name or ID | Level of nested related objects to include: 0 (note only), 1 (note + direct relations), 2 (note + relations + their relations). Choose from the list, or specify an ID using an expression. |
Output
JSON
json- The updated note object returned from the Dalil AI API, including any nested related objects as specified by the depth parameter.
Dependencies
- Dalil AI API key credential for authentication
Troubleshooting
- Ensure the noteId provided is a valid UUID string corresponding to an existing note in the Dalil AI system.
- Verify that the update fields are correctly formatted, especially the body content which supports markdown and is converted to a rich text format internally.
- Check API authentication credentials to avoid authorization errors.
- If specifying depth, ensure the value is within the allowed range (0, 1, or 2) to prevent unexpected API errors.