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 different CRM resources. Specifically, for the Lead Status resource and the Delete operation, it enables users to delete a lead status by specifying its unique ID. This is useful for managing and cleaning up lead statuses that are no longer needed or relevant in your sales pipeline.
Practical examples include:
- Removing obsolete lead statuses to keep your CRM data clean.
- Automating the deletion of temporary or test lead statuses created during workflows.
- Managing lead status lifecycle programmatically as part of larger automation processes.
Properties
| Name | Meaning |
|---|---|
| Status ID | The unique identifier of the lead status to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the lead status was successfully deleted or provide error information if the deletion failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Close.com CRM API.
- The node depends on the Close.com REST API endpoint for lead statuses.
- Proper network access to Close.com's API endpoints is necessary.
- No additional environment variables beyond the API authentication token are indicated.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Status ID will cause the deletion to fail.
- Network connectivity problems can prevent the node from reaching the Close.com API.
- Insufficient permissions associated with the API key may block deletion operations.
Error messages:
"The resource "leadStatus" is not known!"— indicates an incorrect resource parameter; ensure "Lead Status" is selected.- API errors returned from Close.com (e.g., 404 Not Found if the Status ID does not exist).
Resolutions:
- Verify the Status ID is correct and exists in your Close.com account.
- Check API credentials and permissions.
- Ensure stable internet connection and that Close.com API is reachable.