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 interacts with the Gladly API to retrieve a specific conversation item by its unique identifier. It is useful in scenarios where you need to fetch detailed information about a particular conversation within a customer support or communication platform powered by Gladly. For example, you might use this node to display conversation details in a dashboard, analyze customer interactions, or trigger workflows based on conversation content.
Properties
| Name | Meaning |
|---|---|
| Item Id | The unique identifier of the conversation item to retrieve. |
Output
The node outputs JSON data representing the conversation item fetched from the Gladly API. This JSON typically includes all relevant details of the conversation such as messages, participants, timestamps, and metadata associated with that conversation item.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating requests to the Gladly API.
- The base URL for API requests is set to
https://petstore3.swagger.io/api/v3(likely a placeholder; should be replaced with the actual Gladly API endpoint). - The node uses standard HTTP headers for JSON content (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Invalid or missing Item Id: Ensure the "Item Id" property is provided and correctly corresponds to an existing conversation item in Gladly.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- API endpoint issues: Confirm the base URL points to the correct Gladly API endpoint rather than a placeholder.
- Network or connectivity problems: Check network access and firewall settings to allow outbound requests to the Gladly API.
Links and References
- Gladly API documentation (replace with actual URL when available)
- n8n documentation on creating and using API credentials