Node.js project for importing Botmock projects in Dialogflow
Note: The deprecated version of this exporter can be found in the
legacybranch.
Note: prerequisites
Running the following commands should allow you to generate restorable content from your Botmock project.
git clone git@github.com:Botmock/botmock-dialogflow-export.gitcd botmock-dialogflow-exportnpm install-
mv ./sample.env ./.envand edit.envto contain your token and project ids npm start- compress
./outputintooutput.zip
To translate Botmock projects into Dialogflow agents, we make certain assumptions about Botmock project structure:
-
Intents should be used on connectors in the flow as often as is meaningful. Doing so helps the script break up responses across different intent files so as to bypass the repsonse type limits Dialogflow has in place.
-
If there is no intent on the connector from the root message to the first message in the Botmock flow, the script creates one and merges into it all utterances from the default Dialogflow Welcome Intent.
-
When using quick replies or suggestion chips in a project, some intent utterances should be designed to exactly match the content of the options in the content block.
The script maps input context to the path of intents on connectors in the Botmock flow to control conversation paths. In other words, in the flow, a message downstream of a particular intent will require that intent as input context in the created file. Similarly, output contexts are set by the intents on connectors that go out of particular messages.
Note that Dialogflow has a limit of 5 input contexts per intent. Projects should be structured to take account of this fact.
Note also that Dialogflow has a limit of 100 characters in the name of any intent file. The script will begin to use random bytes in file names to prevent this limit from being exceeded.
If Dialogflow issues an error on import, note that you may have to manually edit .json files contained in output.