Actions25
Overview
This node integrates with the EspoCRM API to manage CRM data. Specifically, for the Account - Create operation, it allows users to create a new account record in EspoCRM by specifying required and optional account details.
Common scenarios where this node is beneficial include:
- Automating the creation of customer or partner accounts when new leads are qualified.
- Syncing account data from other systems into EspoCRM.
- Bulk creating accounts based on external data sources.
For example, you could use this node to automatically create an account with its name, contact email, phone number, and billing/shipping addresses whenever a new order is received in your e-commerce platform.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the account (required). |
| Additional Fields | Optional additional information about the account: |
| - Website: Website URL of the account. | |
| - Email Address: Primary email address associated with the account. | |
| - Phone Number: Contact phone number for the account. | |
| - Type: Type/category of the account. Options: Customer, Investor, Partner, Reseller. | |
| - Industry: Industry sector of the account. | |
| - Description: Text description or notes about the account. | |
| - Billing Address: Structured address fields including street, city, state, country, postal code. | |
| - Shipping Address: Structured shipping address fields similar to billing address. |
Output
The node outputs a JSON array where each element corresponds to the created account record returned by the EspoCRM API. Each output object contains the full details of the newly created account as stored in EspoCRM, including any IDs assigned by the system.
No binary data output is produced by this operation.
Dependencies
- Requires connection to an EspoCRM instance via its REST API.
- Requires an API authentication credential configured in n8n to authorize requests.
- The node uses internal helper functions to make HTTP requests to EspoCRM endpoints.
Troubleshooting
Common issues:
- Missing required "Name" property will cause the API request to fail.
- Invalid or missing API credentials will result in authentication errors.
- Providing invalid field values (e.g., wrong data types or unsupported enum options) may cause validation errors from the API.
- Network connectivity issues between n8n and the EspoCRM server can cause request failures.
Error messages:
"The operation "create" is not supported for resource type "account": This indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.- API error responses typically include descriptive messages; check the message for hints on what field or value caused the failure.
Resolution tips:
- Double-check all required fields are provided and correctly formatted.
- Verify API credentials and endpoint URLs.
- Review EspoCRM API documentation for valid field values and constraints.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch operations.
Links and References
- EspoCRM API Documentation
- n8n Expressions Documentation (for dynamic parameter usage)