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 Comment resource with the Get operation, it retrieves details of a specific comment by its ID. This is useful when you want to fetch and display or process information about a particular comment within your CRM workflows.
Practical examples include:
- Fetching a comment's content and metadata to display in a dashboard.
- Retrieving comment details to trigger follow-up actions based on comment content.
- Integrating comment data into reports or notifications.
Properties
| Name | Meaning |
|---|---|
| Comment ID | The unique identifier of the comment to retrieve. |
| Additional Fields | Optional comma-separated list of additional fields to include in the response. |
The Additional Fields property allows specifying extra fields beyond the default ones to be included in the returned comment data.
Output
The node outputs an array of JSON objects representing the retrieved comment(s). Each object contains the comment's data as returned by the Close.com API, including at least the comment ID and any requested fields.
If binary data were involved (not applicable here), it would be summarized accordingly, but this node deals only with JSON data related to comments.
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 provided comment ID being valid.
Troubleshooting
Common issues:
- Invalid or missing Comment ID will cause the node to fail retrieving data.
- Network or authentication errors if the API key is incorrect or expired.
- Specifying invalid field names in Additional Fields may result in incomplete or error responses.
Error messages:
"The resource "comment" is not known!"— indicates a misconfiguration of the resource parameter.- API errors from Close.com will be passed through; check the message for details like "Not Found" or "Unauthorized".
Resolutions:
- Ensure the Comment ID is correct and exists in Close.com.
- Verify that the API key credential is properly set up and has sufficient permissions.
- Double-check the Additional Fields input for typos or unsupported fields.