Wait for Unhandled Intents (Alexa) v3.0.3 Help ​

Starts the Flow when the end user invokes an intent that is not handled by a separate intent Flow in an Alexa session

Note: Steps of the Alexa toolkit work only with existing custom Alexa skills with the method to host your skill's backend resources selected as Provision your own. The skill interaction model must be built with intents and slots on the Amazon developer colsole prior to building solutions with the Alexa toolkit.

How can I use the Step? ​

This Step is used to build a Flow that processes all unhandled intents. An unhandled intent is an intent in the selected skill that is not processed in a separate Flow by the Wait for Intent (Alexa) Step. Use the Wait for Unhandled Intents (Alexa) Step to catch all other intents of the selected skill in a single Flow.

How does the Step work? ​

You select an authorization and a skill. The Flow proceeds down this Step's exit when the end user invokes an intent that is not handled by a Flow with Wait for Intent (Alexa) Step as the first intent in a new Alexa session.

Prerequsites ​

Before building Flows using the Alexa toolkit, you must complete the following steps:

  1. Create a Custom Alexa skill with at least one intent in the Amazon developers console. Read more on how to create Alexa skills here.
  2. Install the Alexa Skill Adapter flow. See the instruction here.
  3. Create an authorization of your OneReach.ai account with the Amazon developer account. See the instructions in the Add an authorization modal of the Authorization section of an Alexa Step.

Alexa Skill Adapter Flow ​

The Alexa Skill Adapter Flow is required to manage the interactions between OneReach.ai and the Amazon developer console. To install it take the following steps:

  1. Add any gateway Step template from the Alexa toolkit to the Flow. For example, a Wait for Intent (Alexa) Step.
  2. Go to the Details tab of the added Step. The Authorization collapsible group contains a warning message with the Install Adapter button. Click to install the adapter Flow. After the installation is completed, a respective message should appear.

Note: In case Alexa Skill Adapter Flow is deactivated or deleted, a respective alert will pop up in the gateway Step of the Flow with a button to fix the problem.

Authorization ​

To set up an authorization, select one of the two options:

Create new authorization ​

To create a new authorization, do the following:

  1. Click the Gear button, then Add, or select to Create new authorization in the dropdown.
  2. A modal window for creating a new authorization will pop up. Follow the instructions in the modal's collapsible. When finished, the created Authorization name should be added to the list in the dropdown. Click Gear > Refresh to update the list of authorizations.
  3. Select respective Authorization name in the dropdown.

Select authorization in current step ​

The Authorization dropdown lists every authorization added to your OneReach.ai account.

  • To choose an authorization, select its name in the dropdown.

The Gear button contains options to Add a new or Delete an existing authorization, as well as to Refresh the list of added authorizations.

In case some changes were made to the authorization, an option to Reauthorize is available. To do that, click the respective button, then:

  1. Click Reauthorize now in the modal window. A new Amazon tab will open.
  2. Enter the login and password of the Alexa developer account.
  3. Click Allow.

Alexa skill ​

If the authorization was successful, the Alexa skill dropdown should contain the list of available custom skills created in the connected Amazon developer console.

  • To choose a skill, select its name in the dropdown.

Click the Refresh button to update the list of available skills. Click the Refresh skill interaction model to get the latest version of the selected skill.

After a skill has been selected, the Step checks the following settings:

Endpoint URL ​

Endpoint URL should be updated automatically by the Step. In case it fails, a link to copy the Endpoint URL becomes available. To set it manually do the following:

  1. Open the Alexa developer console.
  2. Select the respective skill.
  3. Select Build > Endpoint, then select the HTTPS option as the Service Endpoint Type.
  4. Paste the Endpoint URL value in the respective field of the required region.
  5. Set the respective SSL certificate type as My development endpoint is a sub-domain of a domain that has a wildcard certificate from a certificate authority.
  6. Click Save.
  7. Go to Build, then click Build Skill.
  8. Return to the Flow after the skill has been updated and click Refresh skill interaction model.

Auto Delegation ​

Auto Delegation should be turned off automatically by the Step. In case it fails, a respective alert should pop up on Step UI. To turn it off manually do the following:

  1. Open the Alexa developer console.
  2. Select the respective skill.
  3. Select Build > Interfaces.
  4. Turn off the Auto Delegation toggle.
  5. Click Save.
  6. Go to Build, then click Build Skill.
  7. Return to the Flow after the skill has been updated and click Refresh skill interaction model.

Output data ​

This section is optional and allows setting up the properties of the input object that become available as the quick access Merge field values further in the Flow.

The Step outputs the full input JSON object sent by Alexa in its request property. The intent name and slot data are duplicated in the top-level as intentName and slots properties respectively.

To set up this section,

Additional properties ​

By default, the Step includes only the request property in its output. To include additional properties, select them in this section.

Advanced settings ​

The lifespan of the Flow is set in the Flow session timeout field. It defaults to 20 minutes, its limits are between 30 seconds and 48 hours. Examples of acceptable time formats: 32h 3m 12s or 230m.

Merge field settings ​

The output data of the Step is stored in a JSON object under the name provided in the Merge field name. To learn more about Merge fields, their types, and how to work with them, follow this link.

Output example ​

You can select which properties to include in the Output data section.

See below the structure of the Merge field object:

json
{
  "request": {
    "type": "IntentRequest",
    "requestId": "string",
    "timestamp": "2018-04-27T21:36:34Z",
    "locale": "en-US",
    "intent": {
      "name": "string"
    }
  }
}
{
  "request": {
    "type": "IntentRequest",
    "requestId": "string",
    "timestamp": "2018-04-27T21:36:34Z",
    "locale": "en-US",
    "intent": {
      "name": "string"
    }
  }
}

Reporting ​

The Step automatically generates Reporting events during its execution, allowing for real-time tracking and analysis of its performance and user interactions. To learn more about Reporting events, follow this link.

Services dependencies ​

  • Alexa Skill Adapter v3.0.0 or upper

Release notes ​