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 focusing on operations related to comments and comment threads when using the "Comment" resource. The "Get Many Threads" operation retrieves multiple comment threads based on specified filters such as thread IDs or object IDs. This is useful for scenarios where you want to fetch discussions or notes linked to various objects (like leads, contacts, or opportunities) in bulk.
Practical examples include:
- Retrieving all comment threads associated with specific leads to analyze customer interactions.
- Fetching a limited number of recent comment threads for review or reporting.
- Filtering comment threads by specific thread IDs to get detailed information about particular conversations.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching comment threads or limit the number of results returned. |
| Limit | Maximum number of comment threads to return if "Return All" is false. |
| Additional Fields | Optional extra parameters: - Object IDs: Comma-separated list of object IDs to filter threads by. - Thread IDs: Comma-separated list of thread IDs to filter by. - Fields: Comma-separated list of fields to include in the response. |
Output
The output consists of JSON data representing the retrieved comment threads. Each item corresponds to a comment thread with its associated details as provided by the Close.com API. The structure includes standard thread properties and any additional fields requested.
The node does not explicitly handle binary data for this operation.
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- The node uses Close.com's REST API endpoints to fetch comment thread data.
- No other external dependencies are required.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid thread IDs or object IDs may result in empty responses or errors.
- Exceeding API rate limits imposed by Close.com can lead to request failures.
Error Messages:
"The resource \"comment\" is not known!"— This indicates an unsupported resource was selected; ensure "Comment" is chosen.- Network or authentication errors typically indicate issues with the API key or connectivity.
Resolutions:
- Verify that the API key credential is correctly set up and has sufficient permissions.
- Double-check the format and correctness of comma-separated IDs in the input fields.
- Use the "Return All" option carefully to avoid large data requests that might hit rate limits.