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 messages from a specific automation session. It is designed to fetch all messages associated with a given automation session ID, which can be useful for monitoring or processing conversation data within an automated messaging workflow.
Common scenarios include:
- Retrieving chat or message history for a particular automation session.
- Analyzing customer interactions in automated support sessions.
- Integrating session messages into other workflows or databases for further processing.
Example: You have an automation session running for customer support, and you want to extract all messages exchanged during that session to analyze customer sentiment or to log the conversation externally.
Properties
| Name | Meaning |
|---|---|
| Session Id | The unique identifier of the automation session whose messages you want to retrieve. |
Output
The node outputs JSON data containing the messages from the specified automation session. The structure typically includes details about each message such as sender, timestamp, content, and any metadata provided by the Gladly API.
If binary data is returned (e.g., attachments), it would be included accordingly, but based on the provided code and operation, the primary output is JSON-formatted message 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(likely a placeholder). - No additional external dependencies are indicated beyond the Gladly API access.
Troubleshooting
- Invalid Session Id: If the session ID is incorrect or does not exist, the API may return an error or empty result. Verify the session ID before running the node.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network Issues: Connectivity problems to the Gladly API endpoint will cause failures; check network access and endpoint availability.
- Empty Response: If no messages are returned, confirm that the session contains messages and that the session ID is correct.
Links and References
- Gladly API Documentation (replace with actual API docs)
- n8n documentation on creating custom nodes