Actions57
- Agents Actions
- Public Answer Actions
- Answer Management Actions
- Communications Actions
- Customers Actions
- Conversations Actions
- Get Conversations
- Get Conversation
- Patch Conversation
- Create Item
- Get Item
- Delete Item
- Get Media
- Get Voice Transcript
- Create Customer Item
- Delete Customer Item
- Get Conversation Items
- Add Topic To Conversation
- Delete Topic From Conversation
- Add Note To Conversation
- Get Note From Conversation
- Reply To Message
- Redact Content
- Export Actions
- Freeform Topics Actions
- Message Automation Actions
- Proactive Conversations Actions
- Tasks Actions
- User Identity Actions
- Topics Actions
- Webhooks Actions
- Payloads Actions
Overview
This node operation retrieves comments associated with a specific task from the Gladly API. It is useful in scenarios where you want to fetch and display all comments or notes made on a particular task, such as for auditing, collaboration, or tracking purposes. For example, a customer support workflow might use this to gather all comments on a support ticket task before responding.
Properties
| Name | Meaning |
|---|---|
| Task Id | The unique identifier of the task for which comments are requested. |
Output
The output will contain a JSON object representing the list of comments related to the specified task. Each comment typically includes details such as the comment text, author, timestamp, and possibly other metadata depending on the API response structure.
If the node supports binary data output (not evident from the provided code), it would be used to handle attachments or media within comments, but no such indication is present here.
Dependencies
- Requires an API key credential to authenticate requests to the Gladly API.
- The base URL for API requests is set to
https://petstore3.swagger.io/api/v3(likely a placeholder). - Uses an OpenAPI specification (
openapi.json) bundled with the node to define available operations and properties.
Troubleshooting
- Invalid Task Id: If the provided Task Id does not exist or is malformed, the API may return an error or empty result. Verify the Task Id is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is configured properly.
- Network Issues: Connectivity problems can prevent reaching the API endpoint. Check network access and proxy settings if applicable.
- Unexpected Response Format: If the API changes or returns unexpected data, the node might fail to parse comments correctly.
Links and References
- Gladly API Documentation (replace with actual API docs)
- n8n OpenAPI Node Integration Guide