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 integrates with the Cloodo CRM API to manage lead categories among other CRM resources. Specifically, the "Lead Category" resource with the "Update" operation allows users to modify existing lead category records in their Cloodo CRM system. This is useful for keeping lead categorization up-to-date, reflecting changes in business processes or marketing strategies.
Common scenarios include:
- Renaming a lead category to better reflect its purpose.
- Correcting typos or updating naming conventions.
- Adjusting categories as part of CRM data maintenance workflows.
Example: A marketing team wants to rename the lead category "Prospects" to "Potential Clients" to align with new terminology used internally. Using this node, they can update the category name directly via the API without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the lead category to update. |
| Name Lead Categories | The new name to assign to the lead category. |
Output
The node outputs JSON data representing the updated lead category object returned from the Cloodo API after a successful update operation. This typically includes fields such as the category ID, updated name, and possibly metadata like timestamps or status.
No binary data output is involved.
Dependencies
- Requires an active connection to the Cloodo CRM API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/.
Troubleshooting
- Invalid ID: If the provided ID does not correspond to an existing lead category, the API will likely return an error indicating the resource was not found. Verify the ID before running the update.
- Authentication errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n.
- Validation errors: Providing an empty or invalid name may result in API validation errors. Make sure the "Name Lead Categories" field is properly filled.
- Network issues: Connectivity problems to the Cloodo API endpoint will prevent updates. Check network access and API availability.
Links and References
- Cloodo CRM API Documentation (assumed based on base URL)
- n8n documentation on creating custom nodes