Go To Action
This action will redirect the conversation flow to another interaction inside the current behaviour or to an interaction in a completely different behaviour.
The action uses the following settings:
Setting | Description | |
Absolute | This mode will move the flow to a specific behavior and interaction. | ⛔ |
Start | ⛔ | |
Previous | This mode will move the flow to the interaction executed before the current one. | ⛔ |
Fallback | ⛔ | |
Bookmark | ⛔ | |
Behaviour | The target behaviour | ✅ |
Interaction | The target interaction | ✅ |
Cancel Further Execution | Redirect to the selected interaction but stops at the beginning, without executing any action | ⛔ |
Both target behaviour and interaction are parsed to allow for fully dynamic variable based redirection.
If this action fails because of missing interaction or target Xenioo will just ignore the issue an move to the next action in the current queue.
Variables can be specified and combined in the Behaviour and Interaction fields. Using variables you can create dynamic Go-To actions that are based on variable values.
Xenioo is automatically detecting multiple chained jumps or infinite loops. Currently after 25 flow movements per single request, execution is suspended and the result returned to the chatbot.
This action does not have any trigger.
This action produces the following variables after being triggered:
Variable | Description |
goto_source_behaviour | The full name of the behaviour from where this action was originated |
goto_source_interaction | The full name of the interaction from where this action was originated |
Channel specific availability follows the table below:
Channel | Availability |
Facebook | Fully Available. |
WhatsApp | Fully Available. |
Telegram | Fully Available. |
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.
Last modified 8mo ago