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 update the status of an opportunity. Specifically, it allows users to modify an existing opportunity status by changing its label (name). This is useful in scenarios where you want to rename or correct the name of a status category used to track sales opportunities within your CRM.
Practical examples include:
- Renaming a status from "Negotiation" to "In Negotiation" to better reflect your sales process.
- Correcting typos or updating terminology in opportunity statuses without manually editing them in the Close.com interface.
- Automating status updates as part of a larger workflow that manages sales pipelines.
Properties
| Name | Meaning |
|---|---|
| Status ID | The unique identifier of the opportunity status to update. |
| Update Fields | A collection of fields to update for the opportunity status. Currently supports: - Label: The new name/label of the opportunity status. |
Output
The node outputs JSON data representing the updated opportunity status object returned from Close.com after the update operation. This typically includes the updated fields such as the status ID and the new label.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Close.com to authenticate requests.
- The node depends on the Close.com REST API endpoint for opportunity statuses.
- Proper configuration of the Close.com API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Status ID: The node requires a valid status ID to update; ensure the ID exists in your Close.com account.
- Insufficient permissions: The API key must have rights to update opportunity statuses.
- Network or API errors: Temporary connectivity issues or API rate limits may cause failures.
Error messages:
"The resource "opportunityStatus" is not known!"— indicates an invalid resource parameter; verify the resource selection.- Errors related to authentication or authorization usually indicate problems with the API key setup.
- If the node returns an error about missing required parameters, check that the Status ID and at least one update field (Label) are provided.
To resolve these, verify your input parameters, ensure your API key is valid and has appropriate permissions, and check network connectivity.