In this section, you will learn how to deal with entities and slot values provided by your users.
We call user input any additional information your user provides besides an
intent. On Amazon Alexa, input is usually called a
slot, on Google Assistant/Dialogflow an
With the update to Jovo v2, we changed the way you can access input values. Please read more below, or take a look at our migration document.
You can access the complete object of inputs with
this.$inputs, and a specific input by its name:
Each input is an object which looks like this:
For example, if we want to access the value of an input
name provided by the user, we can do so by using
Other parameters (like
id or platform specific elements) can be found in the object as well.
intentMap, there are cases where it might be valuable (due to naming conventions on different platforms or built-in input types) to map different input entities to one defined Jovo
inputName. You can add this to the configuration section of your voice app:
Example: You want to ask your users for their name and created a slot called
name on the Amazon Developer Platform. However, on Dialogflow, you decided to use the pre-defined entity
given-name. You can now use an inputMap to match incoming inputs from Alexa and Google.
With this, you can use
name to get the input with both Alexa and Google requests: