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 allows you to retrieve detailed information about a specific conversation from the Gladly API. It is useful in scenarios where you need to fetch the current state, messages, participants, or metadata of a particular customer support conversation for further processing, analysis, or integration with other systems.
For example, you might use this node to:
- Display conversation details in a custom dashboard.
- Trigger follow-up actions based on conversation status.
- Archive or log conversation data externally.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation to retrieve. |
Output
The node outputs a JSON object containing the full details of the requested conversation. This typically includes fields such as conversation ID, participants, messages, timestamps, status, and any associated metadata provided by the Gladly API.
No binary data output is expected from this operation.
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. - Ensure that the API key has sufficient permissions to read conversation data.
Troubleshooting
- Invalid Conversation Id: If the provided conversation ID does not exist or is malformed, the API will likely return an error indicating the resource was not found. Verify the ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm that the API key is set up correctly in n8n credentials.
- Network Issues: Connectivity problems can prevent the node from reaching the Gladly API. Check network access and proxy settings if applicable.
- API Rate Limits: Excessive requests may trigger rate limiting. Implement retry logic or reduce request frequency if needed.
Links and References
- Gladly API Documentation (replace with actual API docs link)
- n8n Documentation on Credentials