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 a specific comment associated with a task from the Tasks resource. It is useful when you need to fetch detailed information about a particular comment made on a task, such as for auditing, displaying comment content in a UI, or processing comment data further in an automation workflow.
Practical examples include:
- Fetching a user's comment on a project task to display it in a dashboard.
- Retrieving comment details to trigger notifications or updates based on comment content.
- Extracting comment metadata for reporting or analytics purposes.
Properties
| Name | Meaning |
|---|---|
| Task Id | The unique identifier of the task whose comment you want to retrieve. |
| Comment Id | The unique identifier of the specific comment to fetch from the task. |
Output
The output will contain a JSON object representing the requested comment's details. This typically includes fields such as the comment text, author information, timestamps, and any other metadata provided by the API for that comment.
If the node supports binary data output (not indicated here), it would represent attachments or media related to the comment, but this is not evident from the provided code.
Dependencies
- Requires an API key credential to authenticate requests to the external service managing tasks and comments.
- The base URL for API requests is set to
https://petstore3.swagger.io/api/v3(likely a placeholder). - The node depends on an OpenAPI specification (
openapi.json) to define its properties and operations.
Troubleshooting
- Missing or invalid Task Id or Comment Id: Ensure both IDs are correctly provided and correspond to existing entities; otherwise, the API may return errors like "Not Found."
- Authentication errors: Verify that the API key credential is configured properly and has sufficient permissions.
- Network or API endpoint issues: Confirm connectivity to the API base URL and that the endpoint is available.
- Unexpected response structure: If the API changes, the node might fail to parse the comment data correctly.
Links and References
- Gladly API Documentation (Note: This appears to be a placeholder URL; replace with actual API docs)
- n8n documentation on Creating Custom Nodes