EspoCRM
Actions21
Overview
This node is designed to retrieve multiple lead records from a CRM system. It allows users to fetch a list of leads with options to limit the number of results, filter by lead status, and search by name or email. This functionality is useful in scenarios where you want to display or process a subset of leads based on specific criteria, such as generating reports, syncing data, or triggering workflows for certain lead statuses.
Practical examples:
- Fetching the top 10 new leads to assign them to sales representatives.
- Searching for leads containing a specific keyword in their name or email.
- Retrieving all leads currently marked as "In Process" for follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Limit | Maximum number of leads to retrieve (between 1 and 100). |
| Search Query | Text string to search leads by their name or email. |
| Status Filter | Filter leads by their status. Options: All, New, Assigned, In Process, Converted, Recycled, Dead. |
Output
The node outputs an array of lead objects in the json field. Each object represents a lead record retrieved from the CRM system, containing details such as lead name, email, status, and other relevant fields depending on the CRM's data model.
No binary data output is indicated.
Dependencies
- Requires connection to the CRM system that manages leads.
- Needs appropriate API credentials or authentication tokens configured in n8n to access the CRM.
- The node depends on internal operation logic imported from bundled dependencies but does not require additional external libraries beyond those.
Troubleshooting
Common issues:
- Exceeding the maximum allowed limit (over 100) may cause errors; ensure the limit is within the specified range.
- Providing invalid or expired API credentials will result in authentication failures.
- Using unsupported status filters or malformed search queries might return empty results or errors.
Error messages:
- Authentication errors typically indicate missing or incorrect API keys; verify credential setup.
- Validation errors on input properties suggest adjusting the limit or filter values according to allowed options.
- Network or connectivity errors imply checking the CRM service availability and network settings.
Links and References
- Refer to your CRM system’s API documentation for detailed information on lead data structure and available filters.
- n8n documentation on creating and configuring nodes for external APIs.