Overview
This node integrates with the Close CRM platform to retrieve detailed information about a specific lead. It is designed to fetch data for a single lead by its unique identifier within Close CRM. This functionality is useful in scenarios where you want to enrich workflows with up-to-date lead information, such as automating follow-ups, updating records, or triggering actions based on lead details.
Practical examples:
- Automatically retrieving lead details when a new lead is assigned to a sales representative.
- Fetching lead information to personalize email campaigns or notifications.
- Using lead data to update other systems or databases in real-time.
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. The output structure directly reflects the API response for a single lead resource.
There is no binary data output from this node.
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}. - Proper network access to Close CRM's API is necessary.
Troubleshooting
Common issues:
- Invalid or missing Lead ID: The node requires a valid lead identifier; ensure the Lead ID is correct and exists in Close CRM.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network connectivity problems: Ensure that your environment can reach the Close CRM API endpoint.
Common error messages:
- 404 Not Found: The specified Lead ID does not exist. Double-check the Lead ID value.
- 401 Unauthorized: Authentication failed. Check the API key credential configuration.
- 400 Bad Request: The request was malformed, possibly due to an invalid Lead ID format.
Resolving these usually involves verifying input values, credentials, and network settings.
Links and References
- Close CRM API Documentation – Official API docs for lead resources.
- n8n Documentation – General guidance on using credentials and HTTP request nodes.