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 information about a specific automation session within the "Message Automation" resource. It is useful when you want to fetch details of an ongoing or past automation session by providing its unique session ID. Practical use cases include monitoring the status, results, or metadata of message automation workflows in customer support or communication platforms.
Properties
| Name | Meaning |
|---|---|
| Session Id | The unique identifier of the automation session to retrieve. |
Output
The node outputs JSON data representing the details of the requested automation session. This typically includes session metadata such as session status, timestamps, associated messages, and any other relevant session-specific information returned by the Gladly API. There is no indication that binary data is output by this node.
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). - The node uses standard HTTP headers for JSON content (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Invalid Session Id: If the provided session ID does not exist or is malformed, the API may return an error indicating the session was not found. Verify the session ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is properly configured.
- Network Issues: Connectivity problems can prevent reaching the Gladly API endpoint. Check network access and proxy settings if applicable.
- API Endpoint Placeholder: The base URL points to a Swagger petstore example URL, which suggests the actual API endpoint might need configuration. Confirm the correct Gladly API base URL is set in the node or environment.
Links and References
- Gladly API Documentation (for detailed API usage and session data structure)
- n8n Documentation (for general guidance on using custom nodes and credentials)