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 interacts with the Close.com CRM platform, specifically to retrieve multiple opportunity status records when using the "Opportunity Status" resource with the "Get Many" operation. It is useful for workflows that need to fetch lists of opportunity statuses, such as active, won, or lost statuses, optionally filtered by pipeline or limited in number.
Practical examples include:
- Retrieving all opportunity statuses to display in a dashboard.
- Filtering opportunity statuses by a specific sales pipeline.
- Fetching only "won" or "lost" statuses for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or limit the number of returned opportunity statuses. |
| Limit | Maximum number of opportunity statuses to return (used if "Return All" is false). |
| Filter Options | Additional filters to narrow down results: |
| - Pipeline ID | Filter statuses by a specific pipeline ID. |
| - Status Type | Filter statuses by type; options are: Active, Won, Lost. |
| - Fields | Comma-separated list of fields to include in the response for each opportunity status. |
Output
The output is an array of JSON objects representing opportunity statuses retrieved from Close.com. Each object contains fields describing an opportunity status, such as its ID, label, type, and associated pipeline information depending on the requested fields.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for Close.com CRM to authenticate requests.
- The node uses Close.com's REST API endpoints to fetch opportunity status data.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid pipeline ID or status type filter may result in empty responses.
- Exceeding rate limits imposed by Close.com API can cause request failures.
Error messages:
"The resource "opportunityStatus" is not known!"— indicates a misconfiguration or unsupported resource selection.- Network or API errors will typically propagate as error messages; ensure network connectivity and valid API keys.
Resolutions:
- Verify API credentials are correctly configured in n8n.
- Double-check filter values like pipeline IDs and status types.
- Use the "Return All" option carefully to avoid large data loads that might hit API limits.