Actions25
Overview
This node integrates with EspoCRM's API to perform various operations on dynamic entities within the CRM system. Specifically, for the Dynamic resource and Update operation, it updates a record of a specified entity type by modifying one or more fields.
Common scenarios where this node is beneficial include:
- Updating customer information dynamically when new data arrives.
- Modifying custom entity records without hardcoding entity types or fields.
- Automating updates to CRM records based on external triggers or workflows.
For example, you might use this node to update a "Lead" entity's status or contact details dynamically by specifying the entity type and the fields to update.
Properties
| Name | Meaning |
|---|---|
| Entity Type Name or ID | The type of entity to interact with (e.g., Account, Contact, Lead, or any custom entity). Choose from a dropdown list or specify an ID via expression. |
| Record ID | The unique identifier of the record to update. |
| Fields | A collection of fields to update on the record. Each field consists of: - Field Name or ID: The name or ID of the field to update, selectable from a list depending on the entity type. - Field Value: The new value to assign to the field. Multiple fields can be updated in one execution. |
Output
The output is a JSON array where each element corresponds to the result of updating a record. For the Update operation on the Dynamic resource, each output item contains the updated record data as returned by the EspoCRM API after applying the changes.
Example output structure (simplified):
{
"id": "record-id",
"field1": "updated value",
"field2": "updated value",
...
}
If the update is successful, the output reflects the current state of the record post-update.
Dependencies
- Requires an active connection to an EspoCRM instance via an API key or authentication token configured in n8n credentials.
- Uses EspoCRM REST API endpoints to perform CRUD operations.
- Relies on metadata services to dynamically load available entity types and their fields for user selection.
Troubleshooting
- Error loading entity types or fields: This may occur if the API credentials are invalid or the EspoCRM instance is unreachable. Verify API credentials and network connectivity.
- Invalid Record ID: If the specified record ID does not exist, the API will return an error. Ensure the record ID is correct.
- Field validation errors: Attempting to update fields with invalid values or unsupported data types may cause API errors. Confirm field names and acceptable values, especially for enum fields.
- Unsupported operation or resource: The node throws an error if an unsupported operation is selected for the resource. Double-check that "Update" is chosen for the "Dynamic" resource.
- Continue On Fail behavior: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output array.
Links and References
- EspoCRM API Documentation
- n8n Expressions Documentation (for using expressions in property fields)