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 to retrieve multiple comments based on specified filters. Specifically, the "Comment" resource with the "Get Many" operation allows users to fetch a list of comments either by the object they are commenting on or by a comment thread ID.
Common scenarios where this node is beneficial include:
- Aggregating all comments related to a specific CRM object (e.g., a lead or contact) for reporting or analysis.
- Retrieving all comments within a particular discussion thread to display conversation history.
- Integrating comment data into other workflows or systems for enhanced context or automation.
Practical example:
- A sales team wants to pull all comments associated with a particular lead to review communication history before a call.
- A support system fetches all comments in a thread to present the full conversation to an agent.
Properties
| Name | Meaning |
|---|---|
| Filter By | How to filter the comments. Options: • Object ID — Filter comments by the object they comment on. • Thread ID — Filter comments by thread ID. |
| Object ID | The ID of the object to get comments for. Required if filtering by Object ID. |
| Thread ID | The ID of the comment thread. Required if filtering by Thread ID. |
| Return All | Whether to return all matching results or limit the number returned. |
| Limit | Maximum number of results to return when not returning all. Minimum 1, default 50. |
| Additional Fields | Optional extra parameters: • Object IDs (for filtering threads by multiple object IDs) • Thread IDs (for filtering by multiple thread IDs) • Fields (comma-separated list of fields to include in the response) |
Output
The node outputs an array of comment objects in the json field. Each object represents a comment retrieved from Close.com and includes details such as comment content, author, timestamps, and associated object or thread IDs depending on the filter used.
If binary data were involved (not indicated here), it would typically represent attachments or media related to comments, but this node focuses on JSON comment data only.
Dependencies
- Requires an API key credential for Close.com CRM configured in n8n to authenticate requests.
- Relies on Close.com's REST API endpoints for fetching comment data.
- No additional external dependencies beyond the Close.com API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Providing an invalid or missing Object ID or Thread ID will result in no data or errors.
- Exceeding API rate limits imposed by Close.com may cause request failures.
- Incorrect API credentials will prevent successful authentication.
Error messages:
"The resource "comment" is not known!"— This indicates an unsupported resource was selected; ensure "Comment" is chosen.- Errors related to missing required parameters like Object ID or Thread ID — verify that the correct filter and corresponding ID are provided.
- Network or authentication errors — check API key validity and network connectivity.
Resolutions:
- Double-check input parameters and ensure required fields are filled.
- Verify API credentials and permissions.
- Use the "Return All" option carefully to avoid large data loads that might time out.