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 message from an automation session within the "Message Automation" resource. It is useful when you want to fetch detailed information about a particular message in an ongoing or past automation session, such as for auditing, monitoring, or processing purposes.
Practical examples include:
- Retrieving the content and metadata of a customer support message handled by an automated workflow.
- Fetching a message to analyze its status or details before triggering further actions.
- Integrating message data into other systems for reporting or follow-up.
Properties
| Name | Meaning |
|---|---|
| Session Id | The unique identifier of the automation session from which to get the message. |
| Message Id | The unique identifier of the specific message within the automation session to retrieve. |
Output
The node outputs JSON data representing the details of the requested automation session message. This typically includes message content, metadata, timestamps, sender/receiver information, and any other relevant fields provided by the Gladly API for that message.
If the API supports binary data (e.g., attachments), the node would handle it accordingly, but based on the provided code and properties, the primary output is structured JSON data about the message.
Dependencies
- Requires access to the Gladly API endpoint.
- Needs an API authentication token or key configured in n8n credentials (referred generically as an API key credential).
- The base URL for the API is set to
https://petstore3.swagger.io/api/v3in the bundled code, which is likely a placeholder; users must configure the actual Gladly API endpoint. - The node uses standard HTTP headers for JSON communication (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Invalid Session Id or Message Id: If the provided IDs do not exist or are malformed, the API will likely return an error indicating the resource was not found. Verify the correctness of these IDs.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key credential is properly set up in n8n.
- API Endpoint Misconfiguration: The default base URL points to a Swagger petstore example. Users must update this to the actual Gladly API URL to avoid connection errors.
- Network Issues: Connectivity problems can cause timeouts or failed requests. Check network settings and API availability.
Links and References
- Gladly API Documentation (replace with actual URL)
- n8n HTTP Request Node Documentation for understanding how API calls are made
- OpenAPI Specification for details on the API schema used in the node's properties builder