EspoCRMInstall

Overview

This node is designed to delete a Lead entity in the connected system. It is useful when you want to remove a specific lead record by its unique identifier. Common scenarios include cleaning up outdated or incorrect lead data, automating lead lifecycle management, or integrating with other systems where leads need to be deleted based on certain triggers.

For example, if a lead has been marked as invalid or duplicated in your CRM, this node can be used to programmatically delete that lead to maintain data integrity.

Properties

Output

The output will typically contain JSON data confirming the deletion operation. This may include status information or details about the deleted lead, depending on the API's response. There is no indication that binary data is involved in this operation.

Dependencies

• Requires an active connection to the target CRM system.
• Needs appropriate API credentials (such as an API key or authentication token) configured in n8n to authorize the delete request.
• The node depends on the external API supporting lead deletion by ID.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent Lead ID will likely result in an error from the API indicating the lead was not found.
  • Insufficient permissions or missing API credentials can cause authorization errors.
  • Network connectivity problems may prevent the node from reaching the CRM API.

• Error messages and resolutions:

  • "Lead not found": Verify the Lead ID is correct and exists in the system.
  • "Unauthorized" or "Authentication failed": Check that the API credentials are correctly set up and have sufficient permissions.
  • Timeout or network errors: Ensure stable internet connection and that the CRM API endpoint is reachable.

Links and References

• Refer to the CRM system's official API documentation for details on deleting leads.
• Consult n8n documentation on setting up API credentials and using HTTP request nodes if custom integration is needed.