Close CRM icon

Close CRM

Consume Close CRM API

Opportunity Status → Create

AI-generated

Overview

This node operation creates a new opportunity status in the Close CRM system. It allows users to define a label (name) for the opportunity status and specify the status type, which can be Active, Won, or Lost. Additionally, users can optionally assign the opportunity status to a specific pipeline by providing a pipeline ID. This operation is useful for managing and categorizing the stages of sales opportunities within a CRM workflow, helping sales teams track progress and outcomes effectively.

Use Case Examples

  1. Creating a new opportunity status labeled 'Negotiation' with status type 'Active' to represent opportunities currently being negotiated.
  2. Adding a 'Closed Won' status type to mark opportunities that have been successfully closed.
  3. Assigning a new opportunity status to a specific sales pipeline by providing the pipeline ID.

Properties

Name Meaning
Label The label/name of the opportunity status, required to identify the status.
Status Type The type of the opportunity status, indicating whether the opportunity is active, won, or lost.
Additional Fields Optional fields for the opportunity status creation, including the Pipeline ID to assign the status to a specific pipeline.

Output

JSON

  • id - The unique identifier of the created opportunity status.
  • label - The label/name of the created opportunity status.
  • status_type - The type of the created opportunity status (active, won, lost).
  • pipeline_id - The pipeline ID if the opportunity status is assigned to a specific pipeline.

Dependencies

  • Close CRM API authentication token or API key credential

Troubleshooting

  • Ensure that the 'Label' and 'Status Type' fields are provided, as they are required for creating an opportunity status.
  • Verify that the API credentials for Close CRM are correctly configured and have the necessary permissions to create opportunity statuses.
  • If specifying a Pipeline ID, ensure that the pipeline exists and the ID is correct to avoid errors.

Discussion