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 note from a conversation using the Gladly API. It is useful in scenarios where you need to access detailed information or comments attached to a particular conversation, such as customer support interactions or case management systems. For example, a user might want to fetch a note added by an agent during a customer service call to review the context or follow up on the issue.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation from which to retrieve the note. |
| Note Id | The unique identifier of the note to be fetched within the specified conversation. |
Output
The output will contain a JSON object representing the details of the requested note from the conversation. This typically includes fields such as the note content, author, timestamps, and any metadata associated with the note. The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node uses the Gladly API endpoint configured with base URL
https://petstore3.swagger.io/api/v3. - Proper network connectivity to the Gladly API service is necessary.
Troubleshooting
- Invalid Conversation Id or Note Id: If either ID is incorrect or does not exist, the API may return an error indicating that the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up in n8n.
- Network Issues: Connectivity problems can lead to timeouts or failed requests. Check your network connection and firewall settings.
- API Rate Limits: Excessive requests may trigger rate limiting by the Gladly API. Implement retry logic or reduce request frequency if needed.
Links and References
- Gladly API Documentation (general reference for API endpoints and usage)
- n8n Documentation (for configuring credentials and using HTTP Request nodes)