EspoCRM icon

EspoCRM

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

Actions21

Overview

This node is designed to interact with a CRM system to retrieve information about a specific lead. The "Get Lead" operation fetches detailed data for a single lead identified by its unique ID. This is useful in scenarios where you need to access or process information about a particular lead, such as viewing contact details, status, or other custom fields stored in the CRM.

Practical examples include:

  • Fetching lead details before updating or converting the lead.
  • Retrieving lead information to display in a dashboard or report.
  • Using lead data to trigger follow-up actions or notifications.

Properties

Name Meaning
Lead ID The unique identifier of the lead to retrieve. This is required to specify which lead's data should be fetched.

Output

The node outputs a JSON object containing all available data fields for the specified lead. This typically includes standard lead attributes such as name, contact information, status, and any custom fields configured in the CRM. The output structure mirrors the lead record as stored in the CRM system.

If the node supports binary data (not indicated here), it would represent attachments or files related to the lead, but this is not evident from the provided code.

Dependencies

  • Requires connection to the CRM system via an API.
  • Needs an API key or authentication token configured in n8n credentials to authorize requests.
  • The node depends on internal modules (descriptions and operations) that handle the node description and execution logic respectively.

Troubleshooting

  • Missing or invalid Lead ID: The node requires a valid lead ID; ensure this is provided and correctly formatted.
  • Authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions to read lead data.
  • Network issues: Check connectivity to the CRM API endpoint.
  • Lead not found: If the lead ID does not exist, the node may return an error or empty result; confirm the lead ID is correct.
  • Unexpected response format: Ensure the CRM API version matches what the node expects.

Links and References

Discussion