Cloodo CRM icon

Cloodo CRM

Get data from Cloodo API

Actions62

Overview

The node integrates with the Cloodo CRM API to update the status of a lead within the system. Specifically, for the "Lead Status" resource and the "Update" operation, it allows users to modify attributes of an existing lead status entry such as its type, priority, default flag, and label color.

This node is beneficial in scenarios where businesses want to programmatically manage and update the lifecycle stages or statuses of leads in their CRM workflows. For example, automating the transition of a lead from "Pending" to "Inprocess" or marking a lead status as "Converted" after a successful sale.

Practical examples:

  • Automatically updating lead statuses based on external triggers or events.
  • Synchronizing lead status changes from other systems into Cloodo CRM.
  • Managing priority and default flags for lead statuses to influence business logic or UI display.

Properties

Name Meaning
ID The unique identifier of the lead status record to update.
Type Lead Status The category/type of the lead status. Options: Active, Converted, Inprocess, Pending.
Priority Lead Status The priority level assigned to the lead status. Options: 0, 1, 2, 3 (numeric priorities).
Default Lead Status Flag indicating if this is the default lead status. Options: 0 (No), 1 (Yes).
Label Color The color label associated with the lead status, represented as a hex color code (e.g., #fff).

Output

The node outputs JSON data representing the updated lead status object as returned by the Cloodo CRM API. This typically includes fields such as the ID, type, priority, default flag, label color, and possibly timestamps or metadata related to the update.

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 key configured in n8n credentials to authorize requests.
  • The base URL for API requests is https://erp-amz.cloodo.com/v4/.
  • The node expects JSON content-type headers for communication.

Troubleshooting

  • Invalid ID: If the provided ID does not correspond to an existing lead status, the API may return a "not found" error. Verify the ID before updating.
  • Authentication errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n.
  • Invalid property values: Providing unsupported values for properties like "Type Lead Status" or "Priority Lead Status" may result in validation errors. Use only the allowed options.
  • Network issues: Connectivity problems to the Cloodo API endpoint can cause timeouts or request failures. Check network access and API availability.
  • API changes: If the Cloodo API changes its schema or endpoints, the node might fail. Keep the node and API documentation up to date.

Links and References

Discussion