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 Resource "Lead Agent" and Operation "Get Lead Agents," it fetches information about lead agents from the Cloodo system. This is useful in scenarios where users want to automate workflows involving sales or support teams by accessing details of lead agents, such as their identifiers or profiles.
Practical examples include:
- Automatically retrieving a list of lead agents to assign new leads.
- Fetching lead agent details to update records in other systems.
- Integrating lead agent data into reporting dashboards.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the lead agent to retrieve. If left empty, the node may fetch multiple or all lead agents depending on API behavior. |
Output
The node outputs JSON data representing the lead agent(s) retrieved from the Cloodo API. The structure typically includes fields such as the lead agent's ID, name, contact details, and any other metadata provided by the API.
If binary data were involved (e.g., profile images), it would be included in a separate binary output field, but this node focuses on JSON data only.
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 API credentials will cause authentication failures.
- Providing an incorrect or non-existent lead agent ID may result in empty responses or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors usually indicate invalid API keys; verify and update credentials.
- "Not Found" errors suggest the specified lead agent ID does not exist.
- Timeout or connection errors imply network issues; check internet access and API status.
Links and References
- Cloodo API Documentation (Assumed URL based on baseURL)
- n8n Documentation on Creating Custom Nodes