Actions79
- Lead Status Actions
- Pipeline Actions
- Template Actions
- Lead Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Email Template Actions
- Task Actions
- User Actions
- Custom Field Actions
Overview
This node integrates with the Close.com CRM platform, specifically providing operations on various CRM resources. The "Lead" resource with the "Get Many" operation allows users to retrieve multiple lead records from their Close.com account based on specified filters and sorting options.
Typical use cases include:
- Fetching a list of leads that match certain criteria (e.g., status, name) for further processing or reporting.
- Retrieving all leads or a limited subset sorted by creation or update date.
- Integrating lead data into other workflows or systems by pulling filtered lead lists automatically.
For example, a sales automation workflow might use this node to get all new leads created in the last week, ordered by newest first, to trigger follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching leads or limit the number of results. |
| Limit | Maximum number of leads to return if not returning all. Minimum value is 1. |
| Query | JSON-formatted search query to filter leads by fields such as status or name. Example: {"status":"new","name":"acme"} |
| Order By | Field to order the results by. Options include: - Name (A-Z) - Name (Z-A) - Created Date (Newest) - Created Date (Oldest) - Updated Date (Newest) - Updated Date (Oldest) - Status Label (A-Z) - Status Label (Z-A) |
| Additional Fields | Collection allowing specification of additional fields to include in the response as a comma-separated list. |
Output
The node outputs an array of JSON objects representing the retrieved leads. Each object contains lead properties as returned by the Close.com API, including standard fields like name, status, creation date, 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 Close.com configured in n8n to authenticate requests.
- Relies on Close.com's REST API endpoints to fetch lead data.
- No other external dependencies are indicated.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication errors.
- Malformed JSON in the "Query" property can cause request failures.
- Requesting too many records without setting "Return All" may result in truncated data.
- Using unsupported or misspelled field names in "Additional Fields" or "Query" may yield incomplete or empty results.
Error Messages:
"The resource "lead" is not known!"— This indicates an invalid resource selection; ensure "Lead" is selected.- API errors related to rate limits or permissions should be resolved by checking API key scopes and usage.
- JSON parsing errors suggest correcting the syntax of the "Query" input.