Dialogflow Input Action
Last updated
Last updated
This action will parse any user text through Dialogflow engine. The conversation will hold until the user correctly reply to the configured intent or it is skipped using another intent or simple text.
The action uses the following settings:
Setting | Description | |
API Version | Choose either V1 or V2, depending on the version of your Dialogflow Agent. | ⛔ |
API Access Token | The API Token required to integrate your Version 1 Dialogflow Agent or the full Google Auth Json authorization file contents. | ✅ |
Project Id | The Dialogflow Project Id | ✅ |
Language | The language of your agent. Make sure to select the same language you've configured on your agent. | ✅ |
Intent Name | The full name of the intent that will trigger this action. Use an asterisk (*) to trigger on any intent | ✅ |
Fallback Intent | The fallback intent that should be used to retrieve a wrong input reply | ✅ |
Detection Confidence | The minimum confidence required to trigger this action | ⛔ |
Display intent reply in chat | If enabled, Xenioo will display a message bubble with the text you've specified as possible intent reply on Dialogflow. | ⛔ |
Display fallback reply in chat | If enabled, Xenioo will display a message bubble with the text you've specified as possible fallback intent reply on Dialogflow. | ⛔ |
Max Wrong Answers | The maximum number of wrong inputs the user can send before the question is skipped. Set to 0 (zero) to never give up on wrong inputs. | ✅ |
Never Skip Question | The question cannot be skipped by user. The input will repeat indefinitely until the control expression is matched or the maximum number of wrong inputs is reached | ⛔ |
Intent Skip Question | The user can skip the question if his reply matches a specific intent | ⛔ |
Text Skip Question | The user can skip the question if his reply matches a specific text or Regular Expression | ⛔ |
This action is halting the conversation. The chatbot is halted at the input point and will not proceed unless the conditions specified in the settings are met.
Use * (asterisk) in the Intent Name field to catch any DialogFlow intent instead of a specific one.
This action is optimized to use Dialogflow only once per user input. Even using multiple Dialogflow Detection actions will result in a single Dialogflow API Call. Every Dialogflow API call will count as an additional chatbot message.
The Language field is fully parsed to be dynamic so you can set your Dialogflow language dynamically at runtime.
Any integration issue that Xenioo encounters during Dialogflow calls can be found inside each conversation Execution Diagram or inside the chatbot preview Execution Diagram.
On Intent Detected. This action will trigger any child operation as soon as the user input is matching the selected intent with at least the specified confidence.
This action produces the following variables after being triggered:
Variable | Description |
df_detected_action | The action detected during last input |
df_detected_intent | The intent detected during last input |
df_reply | The intent reply received by Dialogflow |
Every entity specified in the detected expression will be translated to a runtime variable named after the entity name.
Channel specific availability follows the table below:
Channel | Availability |
Fully Available. | |
Fully Available. | |
Telegram | Fully Available. |
Web | Fully Available. |
Alexa | Not Available. Out of AI Detection is not supported inside skills. |
Google Assistant | Fully Available. |
Slack | Fully Available. |
API | Fully Available. |
This action can be used only at Bot Global level or Behavior level.
