Actions25
Overview
The node integrates with EspoCRM to update contact records. It allows users to modify various fields of an existing contact by specifying the contact's unique ID and the fields to update. This is useful in scenarios where contact information changes over time, such as updating phone numbers, email addresses, or job titles.
Practical examples include:
- Updating a contact’s email address after receiving new information.
- Changing the associated account for a contact.
- Adding or modifying the contact’s address details.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to update. |
| Update Fields | Collection of fields to update on the contact. Includes: |
| - First Name: Contact’s first name. | |
| - Last Name: Contact’s last name. | |
| - Email Address: Primary email of the contact. | |
| - Phone Number: Contact’s phone number. | |
| - Title: Job title of the contact. | |
| - Account ID: Identifier of the associated account. | |
| - Description: Text description about the contact. | |
| - Address: Nested collection containing: | |
| - Street: Street address. | |
| - City: City name. | |
| - State: State or province. | |
| - Country: Country name. | |
| - Postal Code: Postal or ZIP code. |
Output
The output is a JSON array where each element corresponds to the updated contact record returned from EspoCRM. Each object contains the updated fields of the contact as stored in EspoCRM after the operation completes.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to EspoCRM via its API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- Relies on EspoCRM API endpoints for contacts to perform update operations.
Troubleshooting
Common Issues:
- Invalid or missing Contact ID will cause the update to fail.
- Providing invalid field names or unsupported values may result in API errors.
- Network or authentication failures can prevent successful updates.
Error Messages:
"The operation "update" is not supported for resource type "contact": Indicates a misconfiguration; ensure the correct resource and operation are selected.- API error responses typically include messages about invalid IDs or permission issues; verify credentials and contact existence.
Resolution Tips:
- Double-check the Contact ID is correct and exists in EspoCRM.
- Validate that all fields conform to expected formats (e.g., email format).
- Ensure the API credentials have sufficient permissions to update contacts.
- Use the "Continue On Fail" option in n8n to handle individual item errors gracefully.
Links and References
- EspoCRM API Documentation
- n8n Expressions Documentation (for dynamic parameter usage)