EspoCRM CRUD

Perform CRUD operations in EspoCRM
Join our community

Actions4

Overview

This node enables performing CRUD (Create, Read, Update, Delete) operations on entities within an EspoCRM system via its REST API. It is useful for automating data management tasks such as retrieving records, updating customer information, creating new entries, or deleting obsolete data in EspoCRM directly from n8n workflows.

Typical use cases include:

  • Reading details of a specific CRM record (e.g., Contact or Account) by its ID.
  • Creating new CRM records with specified data.
  • Updating existing records based on their IDs.
  • Deleting records that are no longer needed.

For example, you could use this node to fetch a Contact's details by providing the entity type "Contact" and the record ID, or create a new Account by specifying the entity type and JSON data representing the account fields.

Properties

Name Meaning
Operation The CRUD operation to perform: Create, Read, Update, or Delete.
Entity Type The type of entity to operate on, e.g., "Contact", "Account".
Record ID The unique identifier of the record to read, update, or delete. Required for these ops.
Data JSON-formatted data used for Create or Update operations to specify field values.

Output

The node outputs an array of items where each item's json property contains the response data returned from the EspoCRM API for the corresponding input item.

  • For Read operations, the output JSON contains the retrieved record's fields.
  • For Create and Update, it contains the newly created or updated record data.
  • For Delete, it typically returns confirmation or status of the deletion.
  • In case of errors (if "Continue On Fail" is enabled), the output JSON will contain an error field with the error message.

No binary data is produced by this node.

Dependencies

  • Requires an active EspoCRM instance accessible via its REST API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • Uses HTTP headers including X-Api-Key for authentication and Content-Type: application/json.
  • Optionally supports additional custom HTTP headers provided as a comma-separated string.

Troubleshooting

  • No credentials returned!: Indicates missing or misconfigured API key credentials. Ensure the API key credential is properly set up in n8n.
  • Unknown operation error: Occurs if an unsupported operation is selected. Verify the operation property is one of Create, Read, Update, or Delete.
  • HTTP request failures: Could be due to incorrect EspoCRM URL, invalid record IDs, or network issues. Check the EspoCRM URL and record identifiers.
  • JSON parsing errors: When providing data for Create or Update, ensure the JSON is valid and correctly formatted.
  • If "Continue On Fail" is enabled, errors will be returned in the output JSON under the error key instead of stopping execution.

Links and References

Discussion