Close

Interact with Close.com CRM

Actions79

Lead Status Actions
Pipeline Actions
Template Actions
Lead Actions
Contact Actions
Activity Actions
Meeting Search Actions
- Search
Opportunity Actions
Opportunity Status Actions
Integration Link Actions
Smart View Actions
Comment Actions
Email Template Actions
Task Actions
User Actions
- Get
- Get Many
Custom Field Actions

Overview

This node integrates with the Close.com CRM platform, allowing users to perform various operations on CRM resources such as leads, contacts, activities, opportunities, and more. Specifically, for the Lead - Get operation, it retrieves detailed information about a single lead by its unique ID. This is useful in scenarios where you want to fetch up-to-date lead data from Close.com to use in workflows like lead qualification, enrichment, or reporting.

Practical examples include:

Fetching a lead's details after receiving a webhook notification about a new lead.
Retrieving specific fields of a lead before updating related records in other systems.
Using lead data to trigger personalized email campaigns or notifications.

Properties

Name	Meaning
Lead ID	The unique identifier of the lead to retrieve.
Additional Fields	Optional extra parameters; currently supports:
Fields	A comma-separated list of specific lead fields to include in the response.

Output

The node outputs JSON data representing the lead object retrieved from Close.com. The structure corresponds to the lead resource schema in Close.com, including standard lead attributes and any additional requested fields.

If binary data were involved (not applicable here), it would be summarized accordingly, but this operation returns only JSON data.

Dependencies

Requires an API key credential for authenticating with Close.com.
Needs network access to Close.com's REST API endpoints.
No additional environment variables are explicitly required beyond the API authentication setup.

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 configured and has sufficient permissions.
- Network connectivity problems: The node must reach Close.com's API servers; firewall or proxy issues can block requests.
Error messages:
- "The resource "lead" is not known!" — This indicates an internal misconfiguration or unsupported resource selection; verify the resource parameter.
- API errors returned from Close.com (e.g., 404 Not Found if the lead ID does not exist) will be surfaced as node errors.
Resolution tips:
- Double-check the Lead ID input for correctness.
- Verify API credentials and permissions.
- Use the "Additional Fields" property to limit response size and avoid requesting unavailable fields.