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
The node integrates with the Cloodo CRM API to update project data. Specifically, for the "Project" resource and "Update" operation, it allows users to modify existing projects by specifying the project ID and various optional fields such as status, deadline, client association, category, assigned member, and custom fields.
This node is beneficial in scenarios where project management workflows require programmatic updates to project details, such as changing a project's status when milestones are reached, updating deadlines based on new schedules, or assigning projects to different team members automatically.
Practical examples:
- Automatically marking a project as "Finished" once all tasks are completed.
- Updating the deadline of a project based on client feedback.
- Assigning a project to a new team member after reallocation of resources.
- Adding or modifying custom metadata fields related to a project.
Properties
Name | Meaning |
---|---|
ID | The unique identifier of the project to update. |
Additional Fields | A collection of optional fields to update on the project: |
- Custom Fields Data | JSON string representing custom field key-value pairs to update on the project. |
- Status | The current status of the project. Options: In Progress, Finished, Canceled, On Hold, Not Started. |
- Deadline | The deadline date/time for the project (ISO 8601 format). |
- Client ID | JSON value representing the client associated with the project. |
- Category ID | String representing the category identifier for the project. |
- Member ID | String representing the user/member assigned to the project. |
Output
The node outputs JSON data representing the updated project object as returned by the Cloodo CRM API. This typically includes the project’s updated fields such as ID, status, deadline, client info, category, assigned member, and any custom fields.
There is no indication that the node outputs binary data.
Dependencies
- Requires an active connection to the Cloodo CRM API.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/
. - The node sends and receives data in JSON format with appropriate headers (
Accept: application/json
,Content-Type: application/json
).
Troubleshooting
- Invalid or missing project ID: The update will fail if the provided project ID does not exist or is empty. Ensure the ID is correct and corresponds to an existing project.
- Malformed JSON in Custom Fields Data: The
custom_fields_data
property expects a valid JSON string. Invalid JSON will cause parsing errors. Validate JSON syntax before input. - Incorrect data types: Some fields expect specific formats, e.g.,
deadline
should be a valid ISO 8601 datetime string. Providing incorrect formats may result in API errors. - Authentication errors: If the API key or token is invalid or missing, the node will fail to authenticate. Verify credentials in n8n settings.
- API rate limits or downtime: Temporary failures might occur due to API limits or service unavailability. Retry logic or error handling in workflows can mitigate this.
Links and References
- Cloodo CRM API Documentation (Assumed base URL; consult official docs for detailed API reference)
- n8n Documentation on HTTP Request Node (for understanding how API calls are made)
- JSON validation tools (e.g., https://jsonlint.com) to verify custom fields data input