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 the "Comment" resource is selected. The "Get Thread" operation retrieves a specific comment thread by its ID. This is useful for scenarios where you want to fetch all comments within a particular discussion or thread in Close.com, such as reviewing customer feedback, internal notes, or communication history linked to a lead or opportunity.
Practical examples:
- Fetching the entire conversation thread related to a customer support ticket.
- Retrieving comments on a sales opportunity to review team discussions.
- Accessing notes and remarks made by different users on a project or lead.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the comment thread to retrieve. |
| Additional Fields | Optional extra parameters: |
| - Object IDs | Comma-separated list of object IDs to filter threads by (used mainly in other operations). |
| - Thread IDs | Comma-separated list of thread IDs to filter by (used mainly in other operations). |
| - Fields | Comma-separated list of specific fields to include in the response for customization. |
Output
The output JSON contains the data of the requested comment thread, including all comments and metadata associated with that thread. The structure typically includes thread details such as thread ID, associated objects, comments content, authorship, timestamps, and any additional fields requested.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for Close.com CRM to authenticate requests.
- The node depends on the Close.com API endpoints for comment threads.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Thread ID: The node requires a valid thread ID; providing an incorrect or empty ID will cause errors.
- Authentication failures: Ensure the API key credential is correctly configured and has sufficient permissions.
- Network or API downtime: Temporary connectivity issues with Close.com API can cause request failures.
Error messages:
"The resource \"comment\" is not known!"— This indicates an invalid resource selection; ensure "Comment" is chosen.- Errors related to missing or invalid Thread ID will typically mention the parameter requirement.
- API errors from Close.com will be passed through; check the error message for details like permission denied or not found.
To resolve errors:
- Double-check the Thread ID input.
- Verify API credentials and permissions.
- Retry after some time if the issue is network-related.