EspoCRM
Actions21
Overview
This node updates an existing lead record in a CRM system. It is useful when you want to modify details of a lead such as their name, contact information, status, or other attributes after the lead has been created. Common scenarios include updating lead status based on sales progress, correcting contact details, or adding additional information like industry or website.
For example, if a lead initially came from a web form but later you receive a phone number and want to add it, this node allows you to update that lead's record with the new phone number and any other changed details.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead to update (required). |
| First Name | The first name of the lead (required). |
| Last Name | The last name of the lead (required). |
| The email address of the lead. | |
| Phone | The phone number of the lead. |
| Status | The current status of the lead. Options: New, Assigned, In Process, Converted, Recycled, Dead. |
| Source | The origin of the lead. Options: Call, Email, Existing Customer, Partner, Public Relations, Web Site, Campaign, Other. |
| Industry | The industry associated with the lead. |
| Website | The website URL related to the lead. |
Output
The node outputs JSON data representing the updated lead record. This typically includes all fields of the lead after the update operation, reflecting the new values set by the user. There is no indication that binary data is output by this node.
Dependencies
- Requires connection to the CRM system where leads are managed.
- Needs appropriate API credentials or authentication tokens configured in n8n to authorize update operations.
- The node depends on the external CRM API to perform the update action.
Troubleshooting
Common issues:
- Invalid or missing Lead ID will cause the update to fail because the node cannot identify which lead to update.
- Providing incomplete required fields (First Name, Last Name) may result in errors or rejected requests.
- Network or authentication failures can prevent successful communication with the CRM API.
Error messages:
- "Lead not found" indicates the provided Lead ID does not exist in the CRM.
- "Unauthorized" or "Authentication failed" suggests invalid or missing API credentials.
- Validation errors may occur if required fields are empty or contain invalid data formats.
Resolutions:
- Verify the Lead ID is correct and exists in the CRM.
- Ensure all required fields are filled out properly.
- Check API credentials and permissions.
- Confirm network connectivity to the CRM service.
Links and References
- Refer to your CRM system’s API documentation for detailed information on lead update endpoints and field requirements.
- n8n documentation on creating and configuring nodes for external APIs.