Actions38
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Conclude Session" operation in the WTS Chat node is designed to mark a chat session as concluded or finished. This typically means that no further interaction is expected in the current session unless reactivated. The node allows optionally specifying whether the session should automatically reactivate if a new message arrives from the contact.
This operation is useful in customer support, sales, or any conversational workflow where sessions represent discrete interactions with contacts. For example, after resolving a customer's issue, an agent can conclude the session to indicate closure. If the "Reactivate On New Message" option is enabled, the session will reopen automatically when the contact sends another message, allowing seamless continuation without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the session to be concluded. |
| Reactivate On New Message | Boolean flag indicating whether the session should be reactivated automatically upon receiving a new message from the contact. Defaults to false. |
Output
The output JSON contains the response from the API call that concludes the session. It typically includes details about the updated session status and metadata reflecting the conclusion state. The exact structure depends on the external service's API but generally confirms successful session closure and any related session data.
No binary data output is involved in this operation.
Dependencies
- Requires an active API key credential for authenticating requests to the WTS Chat API.
- The node communicates with the WTS Chat API endpoint
https://api.wts.chat. - Proper configuration of the API key credential within n8n is necessary.
Troubleshooting
- Session ID Empty: If the "Session ID" property is empty or whitespace, the node throws an error prompting to fill in the SessionID field. Ensure the session ID is correctly provided.
- API Errors: Any errors returned by the WTS Chat API during the conclude session request are wrapped and thrown as node errors. Check the API key validity, network connectivity, and session existence.
- Reactivate Option Misuse: While not explicitly error-prone, setting "Reactivate On New Message" incorrectly may cause unexpected session behavior. Use it only if automatic reactivation is desired.
Links and References
- WTS Chat API Documentation (Assumed official docs for more details on session management)
- n8n Documentation on Creating Custom Nodes