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 Status resource with the Get Lead Status operation, it fetches detailed information about a particular lead status by its unique identifier. This is useful in scenarios where you want to programmatically access the current status of leads within your sales pipeline or CRM system.
Practical examples include:
- Automatically retrieving the status of a lead before performing follow-up actions.
- Integrating lead status data into reports or dashboards.
- Synchronizing lead statuses between Cloodo CRM and other systems.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the lead status to retrieve. This string property specifies which lead status record the node will fetch from the Cloodo API. |
Output
The node outputs JSON data representing the details of the requested lead status. The structure typically includes fields such as the lead status ID, name, description, and any other metadata provided by the Cloodo API for lead statuses.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the lead status, but this is not applicable based on the provided code.
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's availability and correct configuration of the API credentials within n8n.
Troubleshooting
Common issues:
- Providing an invalid or empty ID will likely result in an error or no data returned.
- Network connectivity problems or incorrect API credentials can cause authentication failures.
- If the specified lead status ID does not exist, the API may return a "not found" error.
Error messages and resolutions:
- Authentication errors: Verify that the API key or token is correctly set up in n8n credentials.
- Not found errors: Confirm that the ID corresponds to an existing lead status in the Cloodo CRM.
- Timeouts or network errors: Check internet connectivity and API endpoint accessibility.
Links and References
- Cloodo API Documentation (Assumed base URL; consult official docs for detailed API reference)
- n8n documentation on creating custom nodes for further customization guidance