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 "Cloodo CRM" integrates with the Cloodo API to retrieve and manipulate CRM-related data. Specifically, for the Lead Category resource with the Get Lead Category operation, it fetches detailed information about a particular lead category by its unique identifier. This is useful in scenarios where you want to categorize leads based on predefined categories and need to retrieve details about a specific category for reporting, filtering, or further processing.
Practical examples include:
- Fetching a lead category's details to display in a dashboard.
- Using the lead category information to segment leads for targeted marketing campaigns.
- Validating if a lead belongs to a certain category before performing automated workflows.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the lead category to retrieve. This string value specifies which lead category's details will be fetched from the Cloodo CRM system. |
Output
The node outputs JSON data representing the details of the requested lead category. The structure typically includes fields such as the category name, description, creation date, and any other metadata defined by the Cloodo API for lead categories.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the lead category, but this is not applicable based on the provided code and properties.
Dependencies
- Requires an active connection to the Cloodo API endpoint at
https://erp-amz.cloodo.com/v4/. - Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node depends on the Cloodo API being available and responsive.
Troubleshooting
Common issues:
- Invalid or missing ID property: The node will fail to retrieve data if the ID is empty or incorrect.
- Authentication errors: If the API key or token is invalid or expired, the node will return authorization errors.
- Network or API downtime: Connectivity issues or API unavailability will cause request failures.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Verify that the API credentials are correctly set up in n8n.
- "Resource not found" or "404": Check that the provided ID corresponds to an existing lead category.
- Timeouts or network errors: Ensure stable internet connection and that the Cloodo API service is operational.
Links and References
- Cloodo API Documentation (Assumed URL based on baseURL; verify actual docs)
- n8n documentation on Creating Custom Nodes