Overview
This node integrates with the Close CRM platform to retrieve detailed information about a specific lead. It is useful when you want to fetch up-to-date data on a particular lead by its unique identifier, enabling workflows that require lead details for further processing, reporting, or decision-making.
Practical examples:
- Automatically retrieving lead details after a form submission to enrich your database.
- Fetching lead information before sending personalized communications.
- Integrating lead data into dashboards or other systems for real-time insights.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead in Close CRM whose details you want to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the lead's details as returned by the Close CRM API. This typically includes fields such as the lead's name, contact information, status, and any custom fields defined in Close CRM.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Close CRM via an API key credential configured in n8n.
- The node makes HTTP GET requests to the Close CRM API endpoint
https://api.close.com/api/v1/lead/{leadID}where{leadID}is the provided Lead ID.
Troubleshooting
Common issues:
- Invalid or missing Lead ID: Ensure the Lead ID is correctly specified and exists in Close CRM.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check network connectivity and Close CRM service status.
Error messages:
- 404 Not Found: The specified Lead ID does not exist. Confirm the Lead ID is correct.
- 401 Unauthorized: Authentication failed. Recheck the API key credential.
- 400 Bad Request: Input parameters may be malformed; verify the Lead ID format.
Links and References
- Close CRM API Documentation - Leads
- n8n Documentation - HTTP Request Node (for understanding underlying request mechanics)