EspoCRM icon

EspoCRM

Interact with EspoCRM API

Actions25

Overview

The EspoCRM node allows users to interact with the EspoCRM API to manage CRM data programmatically within n8n workflows. Specifically, for the Lead resource and the Get operation, this node retrieves a single lead record by its unique ID from the EspoCRM system.

This node is beneficial in scenarios where you need to fetch detailed information about a specific lead, such as when integrating EspoCRM data into other systems, automating follow-ups, or enriching lead data before further processing.

Example use case:

  • Automatically retrieve lead details when a new event occurs in another system (e.g., a form submission) to trigger personalized marketing campaigns or sales outreach.

Properties

Name Meaning
Lead ID The unique identifier of the lead record to retrieve. This is a required string input.

Output

The node outputs an array of JSON objects representing the retrieved lead record(s). For the Get operation on a Lead, the output JSON object contains all fields of the lead as returned by the EspoCRM API, including standard and custom fields defined in the CRM.

The output structure corresponds directly to the EspoCRM lead entity's data schema, typically including fields like id, name, email, status, and any custom attributes configured in the CRM.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to an EspoCRM instance via an API key credential configured in n8n.
  • The node depends on the EspoCRM REST API being accessible and properly authenticated.
  • No additional external services are required beyond EspoCRM itself.

Troubleshooting

  • Common issues:

    • Invalid or missing Lead ID: The node requires a valid lead ID; providing an empty or incorrect ID will cause errors.
    • Authentication failures: Ensure the API key credential is correctly set up and has sufficient permissions.
    • Network connectivity problems: The node must be able to reach the EspoCRM API endpoint.

  • Error messages:

    • "The operation "get" is not supported for resource type "lead": This would indicate a misconfiguration or unsupported operation, but based on the code, "get" is supported for leads.
    • API errors returned from EspoCRM (e.g., 404 Not Found if the lead ID does not exist): Verify the lead ID is correct.
    • Timeout or connection errors: Check network access and EspoCRM server status.

To resolve these issues, verify input parameters, credentials, and network connectivity.

Links and References

Discussion