Actions25
Overview
This node integrates with EspoCRM to manage CRM data programmatically. Specifically, the "Lead" resource with the "Create" operation allows users to create new lead records in EspoCRM. This is useful for automating lead capture from various sources such as web forms, marketing campaigns, or other systems, ensuring leads are immediately available in the CRM for sales follow-up.
Practical examples include:
- Automatically creating a lead when a visitor fills out a contact form on a website.
- Importing leads from an external marketing platform into EspoCRM.
- Creating leads based on responses from email campaigns or events.
Properties
| Name | Meaning |
|---|---|
| First Name | The first name of the lead. |
| Last Name | The last name of the lead (required). |
| Status | The current status of the lead. Options: Assigned, Converted, Dead, In Process, New, Recycled. (required) |
| Additional Fields | A collection of optional fields to provide more details about the lead: |
| - Account Name | Name of the company associated with the lead. |
| - Address | Detailed address information including street, city, state, country, and postal code. |
| - Description | A textual description or notes about the lead. |
| - Email Address | Primary email address of the lead. |
| - Industry | Industry sector of the lead's company. |
| - Phone Number | Contact phone number of the lead. |
| - Source | Origin of the lead. Options: Call, Campaign, Email, Existing Customer, Other, Partner, Public Relations, Web Site. |
| - Title | Job title of the lead. |
| - Website | Website URL of the lead's company. |
Output
The node outputs an array of JSON objects representing the created lead records. Each object contains the properties of the newly created lead as returned by the EspoCRM API, typically including identifiers, timestamps, and all submitted fields.
If multiple input items are processed, the output will be an array with one entry per item.
No binary data output is produced by this node.
Dependencies
- Requires connection to an EspoCRM instance via its REST API.
- Requires an API authentication credential configured in n8n to authorize requests to EspoCRM.
- The node depends on internal helper functions to make HTTP requests to EspoCRM endpoints.
Troubleshooting
Common issues:
- Missing required fields such as "Last Name" or "Status" will cause errors.
- Incorrect API credentials or connectivity issues will prevent successful creation.
- Invalid values for enumerated fields like "Status" or "Source" may result in API validation errors.
Error messages:
- Errors from the EspoCRM API will be propagated, often indicating missing or invalid data.
- Network or authentication failures will throw errors related to request authorization or connectivity.
Resolution tips:
- Ensure all required fields are provided and valid.
- Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Check network connectivity to the EspoCRM server.
- Use the node’s error output (if continue on fail is enabled) to debug individual record failures.
Links and References
- EspoCRM API Documentation
- n8n Expressions Documentation (for dynamic parameter usage)