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 items from a specific conversation's timeline. It is useful in scenarios where you want to fetch all messages, events, or activities related to a particular customer support conversation for analysis, display, or further processing within an n8n workflow.
For example, a customer service automation might use this node to pull all conversation items before deciding on the next action, such as sending a follow-up message or escalating the issue.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation to retrieve timeline items for. |
Output
The node outputs JSON data representing the timeline items of the specified conversation. This typically includes messages, events, timestamps, and metadata associated with each item in the conversation history.
If the API supports binary data (e.g., attachments), the node would handle it accordingly, but based on the provided code and context, the output focuses on JSON structured conversation items.
Dependencies
- Requires access to the Gladly API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for the API is set to
https://petstore3.swagger.io/api/v3in the bundled code, which appears to be a placeholder; in a real setup, this should point to the actual Gladly API endpoint.
Troubleshooting
- Invalid Conversation Id: If the conversation ID does not exist or is malformed, the API may return an error or empty results. Verify the conversation ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly configured.
- API Endpoint Issues: The base URL in the code is a placeholder. Make sure the node configuration points to the correct Gladly API endpoint.
- Rate Limits: If the Gladly API enforces rate limits, excessive requests may be throttled or blocked.
Links and References
- Gladly API Documentation (replace with actual URL)
- n8n Documentation - Creating Custom Nodes
- OpenAPI Specification