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 allowing users to interact with various CRM resources such as leads, contacts, opportunities, and their statuses. The "Opportunity Status" resource with the "Get" operation enables retrieving detailed information about a specific opportunity status by its ID.
Typical use cases include:
- Fetching the current status details of a sales opportunity to display or process in workflows.
- Automating reporting or notifications based on opportunity status changes.
- Integrating Close.com opportunity status data into other systems or dashboards.
For example, you might use this node to get the name and metadata of an opportunity status before updating related records or triggering follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Status ID | The unique identifier of the opportunity status to retrieve. This is required. |
| Additional Fields | Optional extra parameters for the request: |
| Fields | A comma-separated list of specific fields to include in the response from the API call. |
Output
The node outputs JSON data representing the requested opportunity status object retrieved from Close.com. The structure typically includes fields such as the status ID, label/name, and any additional metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to Close.com via an API key credential configured in n8n.
- The node uses Close.com's REST API endpoints to fetch data.
- No additional external dependencies beyond the Close.com API and n8n's HTTP client are needed.
Troubleshooting
Common issues:
- Invalid or missing Status ID will cause the API call to fail.
- Network or authentication errors if the API key is incorrect or expired.
- Requesting fields that do not exist may result in incomplete or error responses.
Error messages:
"The resource "opportunityStatus" is not known!"— indicates an invalid resource parameter; ensure the resource is set correctly.- API errors related to authorization or bad requests will be surfaced as node execution errors.
Resolutions:
- Verify the Status ID is correct and exists in your Close.com account.
- Check that the API key credential is valid and has sufficient permissions.
- Use the "Fields" property carefully to only request valid field names.