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 Source resource with the Get Leads Source operation, it fetches information about lead sources configured in the Cloodo CRM system. This is useful for workflows that need to analyze or report on where leads originate from, enabling better marketing attribution and sales tracking.
Practical examples include:
- Automatically retrieving all lead sources to populate dropdowns in other systems.
- Generating reports on lead source performance.
- Syncing lead source data with external CRMs or marketing platforms.
Properties
Name | Meaning |
---|---|
ID | The unique identifier of the Lead Source to retrieve. If left empty, the node may fetch multiple or all lead sources depending on the API behavior. |
Output
The node outputs JSON data representing the lead source(s) retrieved from the Cloodo API. The structure typically includes fields such as the lead source ID, name, description, and any other metadata defined by the API.
If binary data were involved (not indicated here), it would represent files or attachments related to the lead source, but this node focuses on JSON data only.
Dependencies
- Requires an active connection to the Cloodo API via an API key credential configured in n8n.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/
. - The node expects JSON responses and sends JSON-formatted requests.
Troubleshooting
- Empty or invalid ID: If the ID property is incorrect or missing when required, the API may return an error or no data. Ensure the ID corresponds to an existing lead source.
- Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify the API key configuration.
- Network issues: Connectivity problems to the Cloodo API endpoint can cause timeouts or failures.
- API changes: If the Cloodo API changes its endpoints or response formats, the node might not work as expected until updated.
Links and References
- Cloodo API Documentation (assumed base URL; check official docs for details)
- General n8n documentation on creating custom nodes