Actions62
- Engagement Actions
- Estimate Actions
- Client Actions
- ClientDetail 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 integrates with the Cloodo CRM API to manage lead agents within a CRM system. Specifically, the "Lead Agent" resource with the "Update" operation allows users to modify existing lead agent records by specifying their unique ID and updating properties such as their status (enabled or disabled). This is useful in scenarios where an organization needs to activate or deactivate lead agents dynamically based on business requirements or changes in personnel.
Practical examples include:
- Disabling a lead agent who is no longer active in the sales team.
- Enabling a newly hired lead agent to start receiving leads.
- Updating lead agent statuses in bulk via workflows to reflect organizational changes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the lead agent record to update. |
| Status | The current status of the lead agent. Options: "Enabled" (active) or "Disabled" (inactive). |
Output
The node outputs JSON data representing the updated lead agent record after the update operation completes successfully. This typically includes fields such as the lead agent's ID, status, and potentially other metadata returned by the Cloodo CRM API confirming the update.
If the node supports binary data output, it would generally relate to attachments or files associated with the lead agent, but this is not indicated in the provided code or properties.
Dependencies
- Requires an API key credential for authenticating requests to the Cloodo CRM API.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/. - Proper configuration of the API credential in n8n is necessary to enable communication with the Cloodo CRM service.
Troubleshooting
- Invalid ID: If the provided ID does not correspond to an existing lead agent, the API will likely return an error indicating the resource was not found. Verify the ID before running the update.
- Authentication errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key is correctly configured and has sufficient permissions.
- Status option mismatch: Providing a status value outside the allowed options ("enabled", "disabled") may result in validation errors. Use only the specified options.
- Network issues: Connectivity problems can prevent the node from reaching the Cloodo API endpoint. Check network settings and firewall rules.
Links and References
- Cloodo CRM API Documentation (Assumed base URL; consult official docs for detailed API reference)
- n8n documentation on Creating Custom Nodes