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, allowing users to perform various operations on CRM resources. Specifically, for the Pipeline - Create operation, it enables creating a new sales pipeline within Close.com. Pipelines in Close.com represent groups of opportunity statuses that help organize and track sales opportunities through different stages.
Typical use cases include automating the creation of new pipelines when setting up new sales processes or dynamically managing pipelines based on business logic. For example, a user might create a pipeline named "New Product Launch" with custom statuses to track opportunities related to that launch.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the pipeline to be created. This is a required string input. |
| Additional Fields | Optional additional settings for the pipeline. Currently supports: |
| Statuses | A JSON array defining opportunity status objects to include in the pipeline. Each object can specify either an existing status by id or define a new status with label and status_type (e.g., active). Example format: [{"id": "status_id"}] or [{"label": "New Status", "status_type": "active"}]. |
Output
The node outputs JSON data representing the newly created pipeline object as returned by the Close.com API. This typically includes fields such as the pipeline's unique identifier, name, and the configured statuses.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for Close.com to authenticate requests.
- The node uses Close.com's REST API endpoints to perform actions.
- No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Improperly formatted JSON in the "Statuses" field may result in request errors.
- Attempting to create a pipeline with a duplicate name might be rejected by the API.
Error Messages:
"The resource \"pipeline\" is not known!": Indicates the resource parameter was set incorrectly or not supported.- API error responses related to invalid input or permissions will be passed through; ensure the API key has sufficient rights.
Resolutions:
- Verify the API key is correctly configured and has necessary permissions.
- Validate JSON syntax in the "Statuses" field before execution.
- Use unique pipeline names to avoid conflicts.