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
This node integrates with the Cloodo CRM system to update lead information. It allows users to modify various attributes of a lead, such as client details, follow-up status, priority, value, assigned agents, source, category, and notes. This is useful in scenarios where sales or marketing teams need to keep lead data current within their CRM, automate updates based on external triggers, or synchronize lead information from other systems.
Practical examples include:
- Automatically updating a lead’s next follow-up status after a call.
- Changing the assigned sales agent when leads are reassigned.
- Adjusting lead priority or value based on new information.
- Adding notes or changing the lead’s status during a workflow.
Properties
Name | Meaning |
---|---|
ID | The unique identifier of the lead to update. |
Additional Fields | A collection of optional fields to update on the lead: |
- Client Email | Email address of the client associated with the lead. |
- Client Name | Name of the client. |
- Next Follow Up | Whether there is a next follow-up scheduled; options: "Yes" or "No". |
- Column Priority | Priority level of the lead (string). |
- Lead Value | Numeric value representing the worth or potential of the lead. |
- Status | Numeric status code representing the lead’s current state. |
- Choose Agents | Numeric ID of the agent assigned to the lead (required field). |
- Lead Source | Numeric ID indicating the origin/source of the lead. |
- Lead Category | Numeric ID categorizing the lead. |
- Note | Text description or note related to the lead. |
Output
The node outputs JSON data representing the updated lead object as returned by the Cloodo API. This typically includes all the lead’s properties after the update operation, reflecting the changes made. The output does not explicitly mention binary data, so it is assumed to be purely JSON.
Dependencies
- Requires an active connection to the Cloodo CRM API.
- Needs an API authentication token or key configured in n8n credentials for accessing the Cloodo API.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/
. - Requests use JSON format with appropriate headers (
Accept: application/json
,Content-Type: application/json
).
Troubleshooting
- Invalid or missing ID: If the lead ID is not provided or incorrect, the update will fail. Ensure the ID corresponds to an existing lead.
- Required fields missing: The "Choose Agents" field is mandatory; omitting it may cause errors.
- Authentication errors: Verify that the API key or token credential is correctly set up and has sufficient permissions.
- Invalid field values: Providing invalid types or out-of-range values (e.g., non-numeric where numeric expected) can cause API rejections.
- Network issues: Connectivity problems with the Cloodo API endpoint will prevent updates.
- To resolve errors, check the error messages returned by the API, validate input data, and confirm credential validity.
Links and References
- Cloodo CRM API Documentation (assumed base URL, consult official docs for detailed API reference)
- n8n documentation on creating custom nodes for further customization guidance