Cloodo CRM icon

Cloodo CRM

Get data from Cloodo API

Actions62

Overview

This node integrates with the Cloodo CRM API to manage lead sources, among other CRM-related resources. Specifically, for the "Lead Source" resource and the "Update" operation, it allows users to update existing lead source records in the Cloodo system. This is useful in scenarios where lead source information needs to be corrected or enriched after initial creation, such as updating the type or details of a lead source.

Practical examples include:

  • Correcting a typo or changing the name/type of a lead source.
  • Updating lead source metadata based on new marketing campaigns or data insights.
  • Synchronizing lead source updates from external systems into Cloodo CRM.

Properties

Name Meaning
ID The unique identifier of the lead source record to update.
Type Leads Source A JSON object representing the updated details or attributes of the lead source.

Output

The node outputs JSON data representing the updated lead source record as returned by the Cloodo API. This typically includes the updated fields of the lead source, confirming the changes made.

If the node supports binary data output (not indicated here), it would represent any file or media associated with the lead source, but this is not evident from the provided code.

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 source, the API will likely return an error indicating the resource was not found. Verify the ID before updating.
  • Malformed JSON in Type Leads Source: Since the property expects JSON, invalid JSON syntax will cause errors. Ensure the JSON is well-formed.
  • Authentication Errors: Missing or incorrect API credentials will result in authorization failures. Confirm that the API key/token is correctly set up in n8n.
  • API Endpoint Issues: Network issues or changes in the API endpoint could cause request failures. Check connectivity and API status.
  • Operation Name Case Sensitivity: Note that the display options for "Type Leads Source" show "Creat" instead of "Create". This might be a typo affecting UI behavior; ensure correct operation names are used.

Links and References

Discussion