Actions25
Overview
This node integrates with EspoCRM to update existing lead records. It allows users to modify various details of a lead such as contact information, company data, status, and source. This is useful in scenarios where lead information changes over time—for example, updating a lead’s phone number after a call, changing the lead status after qualification, or correcting an email address.
Practical examples include:
- Automatically updating lead details from a form submission.
- Syncing lead status changes from another system.
- Enriching lead data with additional company information before sales outreach.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead record to update. |
| Update Fields | Collection of fields to update on the lead. Includes: |
| Account Name | Name of the company associated with the lead. |
| Address | Address details including street, city, state, country, and postal code. |
| Description | Text description or notes about the lead. |
| Email Address | Primary email address of the lead. |
| First Name | Lead’s first name. |
| Industry | Industry sector of the lead’s company. |
| Last Name | Lead’s last name. |
| Phone Number | Contact phone number for the lead. |
| Source | Origin of the lead. Options: Call, Campaign, Email, Existing Customer, Other, Partner, Public Relations, Web Site. |
| Status | Current status of the lead. Options: Assigned, Converted, Dead, In Process, New, Recycled. |
| Title | Job title of the lead. |
| Website | Website URL of the lead’s company. |
Output
The node outputs an array of JSON objects representing the updated lead records. Each object contains the full details of the lead after the update operation, reflecting all changed fields.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to an EspoCRM instance via an API key or authentication token configured in n8n credentials.
- The node uses EspoCRM REST API endpoints to perform updates.
- Proper permissions in EspoCRM are necessary to update lead records.
Troubleshooting
Common Issues:
- Invalid or missing Lead ID will cause the update to fail.
- Insufficient permissions in EspoCRM may result in authorization errors.
- Providing invalid field values (e.g., wrong data types) can cause API validation errors.
- Network connectivity issues between n8n and EspoCRM server.
Error Messages:
"The operation "update" is not supported for resource type "lead": Indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.- API response errors typically include HTTP status codes and messages from EspoCRM, such as 404 Not Found if the Lead ID does not exist, or 400 Bad Request for invalid input.
Resolution Tips:
- Verify the Lead ID exists in EspoCRM.
- Check API credentials and permissions.
- Validate input fields conform to expected formats.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.
Links and References
- EspoCRM API Documentation
- n8n Expressions Documentation (for dynamic parameter usage)