Deploying your apps
Once you have reached the point in your creation to deploy you will find that this is an easy process.
#
Supported platforms for your Narratory agentSince Narratory uses Dialogflow under the hood, any integrations that Dialogflow supports work with Narratory out of the box. This means that deploying your Narratory app on the following platforms is done in a whim:
#
Websites and apps- Dialogflow Messenger: Supporting websites
- Kommunicate: Supporting websites, mobile apps and supports human handover
- Botcopy: Supporting websites and human handover through Janis.ai
#
Instant messaging platforms#
Virtual assistant platforms- Google Assistant - See instructions below
- Alexa - With our Alexa bridge, soon to be released
#
Telephone- Voximplant - See instructions below
- Dialogflow Phone Gateway (US numbers only)
- Genesys Cloud
- Signalwire
- Avaya
- AudioCodes
#
OtherThere are also a number of open-source integrations available on Github, including Skype, SalesForce, Kik, Spark, Twilio, Twitter and Viber.
#
Using Voximplant to interact over phoneVoximplant supports both both incoming calls and doing outgoing calls, we recommend this getting started guide. The only thing you have to do differently is to use the this Voximplant scenario script (remember to change the top variables) as your Voximplant scenario instead of the script posted in the tutorial.
#
Deploying your appOn the Narratory side, deploying means freezing the current stage of your app and giving it a version. This allows you to launch your app to users while working on new features in the same agent.
Note: currently, deploying is only supported for Google Assistant. This is due to the fact that versioning is an experimental and not stable function in Dialogflow at the moment. As the feature matures, it will be supported in Narratory. For other platforms, we recommend using two different agents, one for drafts and one for production.
#
Deploying for Google Assistant- Make sure your app is in a ready state.
- Consider using a Log webhook to make sure you get notified when users trigger fallbacks.
- Decide on a version for your deployed agent. You may want to use the next incremented version number from the Google Assistant deploy page (i.e if you have two deployed versions they would have version "1" and "2" respectively. You would then likely want to use "3" as your next version for consistency. Note, you don't need to use the same version numbers for your Narratory app and for your deployed Google Assistant app, but it is probably a good idea.
- Go to the Fulfillment page in the Dialogflow console and add a header with key: "version" and your version number as value. Don't forget to save.
- From your terminal, run the command
narratory deploy <VERSION_NUMBER>
- Follow the link from the Integrations page in the Dialogflow console to the Google Assistant Console and then follow the guide here.
- Once you have filled in the necessary information, go to the Deploy page and create a new Google Assistant version. We recommend starting off with an Alpha version since you don't need to go through Google's approval process then.
Now, the version will be saved and can be accessed by Alpha testers through Google Assistant. If you have deployed to Beta, you will have to wait for Google's approval process.