Actions39
- 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 Session - ChangeStatus operation updates the status of a given chat session by its ID. This is useful in scenarios where you want to programmatically track or modify the lifecycle state of a chat session, such as marking it as completed, pending, or in progress.
Practical examples include:
- Automatically marking a support chat session as "Completed" after a customer issue is resolved.
- Changing a session's status to "In Progress" when an agent starts handling it.
- Hiding 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 change. |
| Status | The new status to assign to the session. Options: Completed, Hidden, In Progress, Pending, Started, Undefined |
Output
The node outputs a JSON object representing the updated session status response from the WTS Chat API. This typically includes confirmation of the status change and any related session 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 uses the
wtsApicredential to authorize API calls. - Network access to
https://api.wts.chatis required.
Troubleshooting
- Missing or empty Session ID: The node throws an error if the Session ID is not provided or empty. Ensure the Session ID field is filled correctly.
- Invalid or undefined status: If the status is missing or set to "Undefined", the node will throw an error prompting to add a valid status.
- API errors: Any issues returned by the WTS Chat API (e.g., invalid session ID, permission issues) will be surfaced as node errors. Check the API key validity and session existence.
- Network issues: Connectivity problems to the WTS Chat API endpoint can cause failures. Verify network access and proxy settings if applicable.
Links and References
- WTS Chat API Documentation (general reference for API endpoints and status values)
- n8n documentation on creating custom nodes (for understanding node structure and credentials)
This summary focuses exclusively on the Session - ChangeStatus operation within the WTS Chat node based on the provided source code and input properties.