This node allows interaction with the Appointment Scheduling Enterprise (ASE) platform to change the status of an appointment. In the Studio platform, you can use the ASE Change Appointment Status node from the Engageware category.
In the video we’ll show you how to access it and the parameters to configure it:
Here you can download an example flow with the nodes from the Engageware category.
Below you will find the description of the properties you will use in the process and the outputs of each action. 
Properties:
Name (optional): This is the optional name of the node.
Credentials (required): These are the credentials for the Engageware Appointment Schedule Enterprise service. Multiple credentials can be stored, but only one can be active.
In the configuration, you will be asked for:Instance URL: the environment URL.
Username: the API user (API user credentials).
Password: the API user password.
Action (required): These are the available operation types.
Check In: changes the appointment status in the queue to “In Queue” and advances the lifecycle to “CheckedIn.”
Used to indicate that the client has arrived and is waiting in the queue to be served.Start: changes the appointment status in the queue to “Servicing” and advances the lifecycle to “InProgress.”
Used to indicate that the client has started being served.No Show: changes the appointment status in the queue to “No Show” and advances the lifecycle to “No Show.”
Used to indicate that the client did not attend the appointment.Complete: changes the appointment status in the queue to “Complete” and advances the lifecycle to “Completed.”
Used to indicate that the appointment has ended.
Confirmation Number (required): the appointment identifier code obtained when scheduling.
Outputs:
msg.payload.metadata.EW_ASE_ChangeAppointmentStatusResponse: returns status 0 if the status change is successful. In case of error, the “error” property will be returned.