3.2.1 Launch Node

The Launch node receives the request to start the application from Echo Google home, Mobile Chat, Web Chatbot, Alexa, Voice assistants, or a phone call. It does not provide any command mapping to an intent.

The Launch node receives the request when the user starts the application and the connected say node text is displayed to the user which is used to kick start the conversation.

Launch Node Parameters

Double click the launch node to edit its properties.

Skill. The current project name.
Invocation. You can rename the name of this node. It is recommended to leave this field empty.
State. The available states in the current project. You can add states here to use it in the Experience Designer flows.
Analytics. Enable the checkbox Disable Analytics Logging to remove the launch node logs from insights.
Endpoint. The endpoint of the project. This URL is used as a webhook URL for Alexa and Dialogflow.
For Dialogflow, go to Dialogflow and select fulfillment from the side menu. Enable Webhook and use this URL to link the Dialogflow agent with the Orbita project.
Auth URL. This URL can be used to link orbita users' accounts with Alexa and Dialogflow.
Access Token. The access token URL.

For Alexa, go to https://developer.amazon.com/ and select account linking on the left side menu.

For Dialogflow, go to https://console.actions.google.com/ > Develop tab > Account Linking from the side menu.

Creating a Launch Node For an Existing Skill

Drag the Voice Launch node onto the Canvas and double-click to edit.

You can only have one Launch node for a project
To initiate the conversation (interaction) the Launch node should be present in a project.

Video Content

Watch a demonstration of the launch node using a chatbot

https://cdn.orbita.cloud/assets/orbita/experiencedesigner/launchnode.mp4

Supporting Documentation

No additional supporting documentation

Useful Links

http://orbita.ai

Orbita Help Center