Actions38
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The node interacts with the WTS Chat API to manage chat sessions and their statuses. Specifically, the "Update Status Session" operation allows users to update the status of a particular chat session by providing the session ID and the new status value.
This node is beneficial in scenarios where automated workflows need to track or modify the lifecycle state of chat sessions, such as marking a session as completed after customer support interaction, hiding inactive sessions, or updating progress states for reporting and analytics.
Practical examples:
- Automatically mark a chat session as "Completed" once a support ticket is resolved.
- Change a session's status to "In Progress" when an agent starts interacting with a customer.
- Hide sessions that are no longer relevant from active views by setting their status to "Hidden".
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the chat session whose status you want to update. |
| Status Session | The new status to assign to the session. Options: Completed, Hidden, In Progress, Pending, Started, Undefined |
Output
The output is a JSON object representing the updated session status response from the WTS Chat API. It typically includes details confirming the status change and any related metadata returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the WTS Chat API.
- The node depends on the external WTS Chat service endpoints to perform session status updates.
- Proper configuration of the API base URL (
https://api.wts.chat) and valid credentials is necessary.
Troubleshooting
- Missing or invalid Session ID: If the session ID parameter is empty or invalid, the node throws an error indicating that both sessionId and status are required.
- Invalid status value: Selecting "Undefined" or not providing a valid status option results in an error prompting to add a valid status.
- API errors: Network issues, invalid API keys, or permission problems will cause the node to throw errors from the underlying API call. Ensure the API key is correct and has sufficient permissions.
- General validation: Always ensure all required fields are filled before execution to avoid runtime errors.
Links and References
- WTS Chat API Documentation (hypothetical link for reference)
- n8n documentation on Creating Custom Nodes