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 you to update comments associated with CRM records. The "Update Comment" operation lets you modify the body of an existing comment by specifying its unique ID and providing new content. This is useful for correcting or enhancing notes attached to leads, contacts, or other entities within Close.com.
Practical examples include:
- Updating a comment to add additional details after a phone call.
- Correcting typos or formatting in previously entered comments.
- Enhancing comment content with rich text formatting supported by Close.com.
Properties
| Name | Meaning |
|---|---|
| Comment ID | The unique identifier of the comment you want to update. |
| Update Fields | Collection of fields to update on the comment. Currently supports: |
| Body | The new content of the comment. Supports rich text formatting (e.g., bold, italics). |
Output
The node outputs JSON data representing the updated comment object as returned by the Close.com API. This typically includes the comment's ID, updated body content, timestamps, author information, and any other metadata provided by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- The node depends on the Close.com API being accessible and the user having permissions to update comments.
- No additional external dependencies beyond the Close.com API and n8n's HTTP client are required.
Troubleshooting
Common issues:
- Invalid or missing Comment ID will cause the update to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Providing an empty or improperly formatted body may cause the API to reject the update.
Error messages:
"The resource "comment" is not known!"— indicates the resource parameter was set incorrectly.- API errors related to authentication or validation will be passed through; ensure your API key is valid and the comment ID exists.
Resolutions:
- Double-check the Comment ID value is correct and corresponds to an existing comment.
- Verify that the API key credential has sufficient rights to update comments.
- Ensure the "Body" field contains valid text and respects any formatting rules imposed by Close.com.