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 manage opportunity statuses. Specifically, the "Create" operation under the "Opportunity Status" resource allows users to add new opportunity status labels to their sales pipelines. This is useful for customizing the stages or states that an opportunity can have within a pipeline, such as marking opportunities as active, won, or lost.
Practical examples include:
- Adding a new custom status like "Negotiation" or "Proposal Sent" to better reflect your sales process.
- Creating standard statuses such as "Won" or "Lost" programmatically during automation workflows.
- Associating a status with a specific sales pipeline by providing its ID.
Properties
| Name | Meaning |
|---|---|
| Label | The name or label of the opportunity status to create (e.g., "Negotiation", "Closed Won") |
| Status Type | The type/category of the opportunity status. Options: Active, Won, Lost |
| Additional Fields | Optional extra fields; currently supports: Pipeline ID — the ID of the pipeline this status belongs to |
Output
The node outputs JSON data representing the created opportunity status object returned from Close.com API. This typically includes details such as the status ID, label, type, and associated pipeline if provided.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for Close.com CRM configured in n8n to authenticate requests.
- Relies on Close.com REST API endpoints to create opportunity statuses.
- No additional external dependencies beyond the Close.com API and n8n's HTTP client.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing an invalid pipeline ID may result in API errors or failure to associate the status correctly.
- Duplicate labels might be rejected by the API depending on Close.com's rules.
Error messages:
"The resource "opportunityStatus" is not known!"— indicates the resource parameter was incorrect or unsupported.- API error responses related to validation or authentication will be passed through; check the message for details.
Resolutions:
- Verify API credentials are correct and have sufficient permissions.
- Ensure pipeline IDs exist and are valid in your Close.com account.
- Use unique labels or check existing statuses before creating new ones.