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 to retrieve multiple lead status records. The "Get Many" operation under the "Lead Status" resource fetches a list of lead statuses, which represent different stages or states that leads can be in within the CRM.
Typical use cases include:
- Synchronizing lead status data from Close.com into other systems.
- Reporting or analytics workflows where you need to process or filter leads based on their status.
- Automating marketing or sales processes that depend on current lead statuses.
For example, you might use this node to pull all lead statuses and then trigger different actions depending on whether leads are "New", "Contacted", or "Qualified".
Properties
| Name | Meaning |
|---|---|
| Return All | Boolean flag to determine if all lead statuses should be returned or limited by a number. |
| Limit | Maximum number of lead statuses to return when "Return All" is false (minimum 1). |
| Filter Options | Additional filtering options: a comma-separated list of specific fields to include in the response. |
Output
The node outputs an array of JSON objects representing lead statuses. Each object contains fields describing a lead status, such as its ID, label, and any other requested fields.
If binary data were involved (not applicable here), it would typically represent files or attachments related to the lead status, but this node only returns JSON data.
Dependencies
- Requires an API key credential for Close.com CRM to authenticate requests.
- The node uses Close.com's REST API endpoints to fetch lead status data.
- No additional external dependencies beyond the Close.com API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Authentication errors due to invalid or missing API credentials.
- Exceeding API rate limits imposed by Close.com.
- Requesting fields that do not exist or are misspelled in the "Fields" filter option.
- Setting "Limit" to zero or a negative number (minimum is 1).
Error messages:
"The resource "leadStatus" is not known!"— This indicates the resource parameter was incorrectly set; ensure "Lead Status" is selected.- API errors returned from Close.com will be passed through; check the error message for details like authentication failure or invalid parameters.
Resolutions:
- Verify API credentials and permissions.
- Use valid field names in the filter options.
- Adjust the limit to a positive integer.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.