Actions39
- Panel Actions
- Message Actions
- Chatbot Actions
- Contact Actions
- Sequence Actions
- Session Actions
Overview
This node updates an existing session in the WTS Chat system. It allows users to modify various session attributes such as status, end time, number, department, assigned user, and metadata. This operation is useful for managing and maintaining session details dynamically, for example, updating the session status after a customer interaction or reassigning the session to a different department or user.
Use Case Examples
- Updating the status of a session to 'Completed' after a support interaction.
- Changing the department responsible for a session to route it to the correct team.
- Adding or modifying metadata associated with a session for better tracking and reporting.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the session to be updated. |
| Fields | The specific fields of the session that should be updated, such as Status, EndAt, Number, DepartmentId, UserId, Metadata, etc. |
| Department Name or ID | The department to assign to the session when updating the DepartmentId field. Can be selected from a list or specified by ID. |
| User Name or ID | The user to assign to the session when updating the UserId field. Can be selected from a list or specified by ID. |
| EndAt | The new end time for the session, specified as a date and time. |
| Number | The new number to associate with the session. |
| Status Session | The new status to set for the session, such as Completed, Hidden, In Progress, Pending, Started, or Undefined. |
| Metadata | Key-value pairs to update the metadata of the session. |
Output
JSON
json- The updated session object returned from the WTS Chat API after the update operation.
Dependencies
- WTS Chat API key credential
Troubleshooting
- Ensure the Session ID is provided and not empty; otherwise, the node will throw an error indicating the SessionID is empty.
- When updating fields, ensure the values conform to expected formats, e.g., date-time for EndAt, valid status values for Status.
- If the API key credential is missing or invalid, the node will fail to authenticate with the WTS Chat API.
- If the DepartmentId or UserId fields are updated, ensure the selected department or user exists and is valid to avoid API errors.