EspoCRM
Actions21
Overview
The node is designed to create a new Account record in a CRM system. It allows users to input essential details about a company or organization, such as its name, type of business relationship, and additional optional information like website, industry, phone number, billing address, and description. This node is beneficial for automating the process of adding new accounts into a CRM database, ensuring consistent data entry and integration with other workflows.
Practical examples include:
- Automatically creating customer accounts from form submissions on a website.
- Adding new partner organizations when onboarding strategic alliances.
- Logging investor details during financial tracking processes.
Properties
| Name | Meaning |
|---|---|
| Account Name | The official name of the company or organization (e.g., "Acme Corporation" or "Tech Solutions Ltd"). Required field. |
| Account Type | The business relationship type categorizing how this account relates to your organization. Options: Customer, Investor, Partner, Reseller. Default is Customer. |
| Additional Fields | Optional extra information about the account: |
| - Website | Company website URL (e.g., https://www.company.com). |
| - Industry | The industry sector the company operates in (e.g., Technology, Manufacturing, Healthcare). |
| - Phone Number | Main phone number for the account (e.g., +1-555-123-4567). |
| - Billing Address Street | Street address for billing purposes (e.g., 123 Main Street). |
| - Billing Address City | City for billing address (e.g., New York). |
| - Billing Address Country | Country for billing address (e.g., United States). |
| - Description | Additional notes or description about the account. |
Output
The node outputs JSON data representing the newly created Account record. This typically includes all the fields provided during creation along with any system-generated identifiers or metadata confirming successful creation.
If the node supports binary data output (not indicated here), it would summarize that binary data represents attachments or files related to the account, but no such indication exists in the provided code.
Dependencies
- Requires connection to the target CRM system where the Account records are stored.
- Needs appropriate API credentials or authentication tokens configured within n8n to authorize the creation operation.
- The node depends on internal modules for descriptions and operations, which handle the detailed execution logic.
Troubleshooting
Common Issues:
- Missing required fields such as Account Name may cause the operation to fail.
- Incorrect or missing API credentials will prevent successful communication with the CRM.
- Invalid URLs or improperly formatted phone numbers might be rejected by the CRM backend.
Error Messages:
- Authentication errors indicate issues with API keys or tokens; verify credentials and permissions.
- Validation errors usually specify which required property is missing or incorrectly formatted; ensure all mandatory fields are correctly filled.
- Network or timeout errors suggest connectivity problems; check network settings and CRM availability.
Links and References
- Refer to your CRM system’s API documentation for detailed requirements on Account creation.
- Consult n8n documentation on setting up API credentials and using custom nodes for external services.