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 perform operations related to "Lead Status" entities. Specifically, the "Get" operation retrieves detailed information about a particular lead status by its unique ID. This is useful when you want to fetch metadata or properties of a lead status for reporting, automation, or synchronization purposes.
Common scenarios:
- Fetching the details of a specific lead status to display in dashboards or reports.
- Using lead status data to conditionally route leads in workflows.
- Synchronizing lead status information between Close.com and other systems.
Example:
You have a workflow that processes leads and needs to check the current status label or other fields of a lead status by its ID before deciding the next steps. This node can retrieve that information dynamically.
Properties
| Name | Meaning |
|---|---|
| Status ID | The unique identifier of the lead status to retrieve. Required for this operation. |
| Additional Fields | Optional collection of extra parameters; currently supports: |
| - Fields | Comma-separated list of specific fields to include in the response from Close.com API. |
Output
The node outputs JSON data representing the requested lead status object as returned by the Close.com API. The structure typically includes fields such as the status ID, label, description, and any other requested fields specified in the "Fields" property.
If binary data were involved (not applicable here), it would be summarized accordingly, but this node deals only with JSON data.
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- 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 client.
Troubleshooting
- Missing or invalid Status ID: The operation requires a valid lead status ID. Ensure the ID is correct and exists in your Close.com account.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions to access lead statuses.
- Network or API errors: Temporary network issues or API rate limits may cause failures. Retry or check Close.com service status.
- Invalid fields parameter: If specifying additional fields, ensure they are valid field names recognized by the Close.com API.
Common error messages:
"The resource "leadStatus" is not known!"— indicates a misconfiguration of the resource parameter; ensure "Lead Status" is selected.- API error responses will be passed through; check the message for details like unauthorized access or not found.