EspoCRM icon

EspoCRM

Interact with EspoCRM API to manage accounts, contacts, leads, and opportunities. Create, read, update and delete CRM records.

Overview

This node allows you to create a new lead record in a CRM system. It is useful for automating the process of adding potential customer information into your sales pipeline. For example, when a new contact fills out a form on your website or when you receive a lead from a marketing campaign, this node can automatically add that lead's details into your CRM.

Properties

Name Meaning
First Name The first name of the lead (required).
Last Name The last name of the lead (required).
Email The email address of the lead.
Phone The phone number of the lead.
Status The current status of the lead. Options: New, Assigned, In Process, Converted, Recycled, Dead. Default is "New".
Source The origin of the lead. Options: Call, Email, Existing Customer, Partner, Public Relations, Web Site, Campaign, Other. Default is "Web Site".
Industry The industry associated with the lead.
Website The website URL related to the lead.

Output

The node outputs JSON data representing the newly created lead record. This typically includes all the fields provided as input along with any additional metadata assigned by the CRM system, such as a unique identifier for the lead. The output does not include binary data.

Dependencies

  • Requires connection to a CRM system API.
  • Needs an API key or authentication token configured in n8n credentials to authorize requests.
  • Proper network access to the CRM service endpoint.

Troubleshooting

  • Common issues:
    • Missing required fields like First Name or Last Name will cause errors.
    • Invalid or expired API credentials will prevent successful creation.
    • Network connectivity problems may cause timeouts or failures.
  • Error messages:
    • Authentication errors indicate invalid or missing API keys; verify and update credentials.
    • Validation errors usually point to missing or incorrectly formatted input properties; ensure all required fields are filled correctly.
    • API rate limits or server errors require checking CRM service status or adjusting request frequency.

Links and References

  • Refer to your CRM system’s API documentation for detailed field definitions and authentication setup.
  • n8n documentation on creating custom nodes and managing credentials.

Discussion