Actions62
- Client Actions
- ClientDetail Actions
- Engagement Actions
- Estimate Actions
- Lead Actions
- Lead Agent Actions
- Lead Category Actions
- Lead Source Actions
- Lead Status Actions
- Proposal Actions
- Project Actions
- Task Actions
- Note Actions
Overview
This node allows users to create a new Note within a specified project in the Cloodo CRM system. It is useful for adding contextual information, comments, or updates related to projects, tasks, tickets, proposals, milestones, or other categories tracked in the CRM. For example, a project manager might use this node to add a note summarizing recent client feedback or a developer could log task-specific notes for team visibility.
Properties
| Name | Meaning |
|---|---|
| Project_id | The unique identifier of the project to which the note will be attached. |
| Title | The title or headline of the note. |
| Type | A boolean option indicating a specific type attribute of the note (true or false). |
| Details | The detailed content or body text of the note. |
| Category | The classification of the note; options include Task Note, Project Note, Client Feedback, Manager Note, Ticket Note, Proposal Note, Milestone Note, and Other. |
| Users ID | The user IDs associated with the note, typically representing the authors or relevant users. |
| Additional Fields | Optional extra settings: - Ask to re-enter password (true/false) - Visible To Client (true/false) |
Output
The node outputs JSON data representing the newly created note object as returned by the Cloodo API. This JSON typically includes fields such as the note's ID, project association, title, details, category, user associations, timestamps, and any flags set via additional fields. There is no binary output.
Dependencies
- Requires an active connection to the Cloodo CRM API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/.
Troubleshooting
- Missing Required Fields: Ensure all required properties like
Project_id,Title,Details, andUsers IDare provided; otherwise, the API may reject the request. - Invalid User IDs Format: The
Users IDfield expects a JSON-parsable string; invalid formatting can cause errors. - API Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network Issues: Check connectivity to the Cloodo API endpoint if requests time out or fail.
- Category Value Errors: Use only the predefined category options to avoid validation errors.
Links and References
- Cloodo CRM API Documentation (assumed based on base URL)
- n8n Documentation on Creating Custom Nodes