Flow Control Action
Last updated
Last updated
Use this action to stop the flow execution and return to the user. You can use this action as a mean to stop multiple actions or to suspend temporary or indefinitely any user interaction.
The action uses the following settings:
Setting | Description | |
End Execution | Setting this flow state will end any other action or operation execution and send back control to the user | |
Ban User | Setting this flow state will start the user ban procedure from the channel | |
Channel User Id | If specified, the indicated user id will be banned from the channel, otherwise the current user will be banned | |
Band Duration | The duration of the ban, in minutes. A duration equal to zero means a permanent ban. | |
Message | The message that will be displayed to the user before the ban becomes active |
The Channel User Id can be used to specify a very specific user ban and is currently supported only in Telegram. You can use this setting in a Telegram group chat to ban a very specific user.
All other channels ban are managed directly by Xenioo by locking the chatbot interaction with the specified user.
This action has no trigger.
This action does not produce any variable.
Channel specific availability follows the table below:
Channel | Availability |
Fully Available. | |
Fully Available. | |
Telegram | Fully Available. Channel direct ban. |
Web | Fully Available. |
Alexa | Fully Available. |
Google Assistant | Fully Available. |
Slack | Fully Available. |
API | Fully Available. |
This action can be used only inside interactions and not as child of other actions.
