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 interacts with the Close.com CRM platform, specifically allowing operations on various resources including comments. The "Delete" operation for the "Comment" resource enables users to remove a comment by its unique identifier. This is useful in scenarios where outdated, incorrect, or irrelevant comments need to be cleaned up from the CRM system to maintain data accuracy and clarity.
Practical examples:
- Automatically deleting comments related to closed or cancelled deals.
- Removing spam or inappropriate comments from contact records.
- Cleaning up test or temporary comments created during data import or testing phases.
Properties
| Name | Meaning |
|---|---|
| Comment ID | The unique identifier of the comment to delete |
Output
The output of this node operation is JSON data representing the result of the delete action. Typically, this will confirm whether the deletion was successful or provide details about the deleted comment. If an error occurs, the output may contain an error message describing the issue.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Close.com CRM API.
- The node depends on the Close.com API being accessible and the provided comment ID being valid.
- Proper permissions are required on the API key to perform delete operations on comments.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Comment ID will cause the operation to fail.
- Insufficient API permissions can lead to authorization errors.
- Network connectivity problems may prevent communication with the Close.com API.
Common error messages:
"The resource "comment" is not known!"— indicates an invalid resource selection; ensure "comment" is selected.- Errors containing
"error"in the output JSON indicate failure reasons such as invalid ID or permission issues.
Resolutions:
- Verify the Comment ID exists and is correctly formatted.
- Check that the API key has delete permissions for comments.
- Ensure network access to Close.com API endpoints.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.