One of the intents that is displayed correctly in the chat-bot (the text is there) has got empty inside. We need to change the text in there but can't.
http://prntscr.com/pn1yed
With training phrase, the intent is not found. The screenshot above.
Dialogflow API v1 is shutdown from 23rd OCT 2019.
You will have to switch to DialogFlow Api V2.
Here is a migration guide, you can migrate to DF API V2 using this official guide.
Related
Initial Situation
We have a published Google Action with Version V1. It has intents A and B and uses the Dialogflow ES - Google Action integration. The fulfillment URL for the intents is example.com/v1. It has been reviewed and is in Production and working fine.
New Version Expected Outcome
We want to deploy a new version V2, which has an additional intent C and a new fulfillment url example.com/v2.
According to the documentation
New Action submissions create a snapshot of your Dialogflow agent at
the time of submission. Future edits to your Dialogflow agent do not
impact this snapshot (or version). For edits to go live, you must
submit your draft for alpha, beta, or production release in the
Actions Console.
In the past this also worked. We imported a new version of the dialogflow agent with a new fulfillment URL and the existing production version was not touched and we could submit a new version for alpha, beta review or production review.
Current Problematic Behavior
The production version V1 is not frozen anymore but seems to be directly linked to the Dialogflow draft. As soon as we import the new action or even just change the fulfillment URL this change is reflected also in production without any review.
We've verified this both via selecting a version in the Google Actions simulator, and also by using Google Assistant on a device with another account which is neither developer nor beta tester and being able to invoke the new Intent C and being redirected to the new version of the backend.
One observation is that in the past the versions released through submitting a version in the Google Actions console showed up in dialogflow under published versions with a note Version created from Actions on Google console. However, for the last production version and subsequent alpha versions this entry is missing.
The issue is currently also being tracked in the dialogflow issue tracker here: https://issuetracker.google.com/issues/217720434
I am writing this here because the Google Actions support is very adamant that I should use these "community forums" for technical issues.
We are interested in finding a workaround as this currently blocks submitting a beta version with the new functionality unless we just make the new functionality also available publicly inadvertantly.
I have some entities and intent sentences that I could use right away. It is tedious to input them by hand in the UI. I've seen that the output is just a bunch of JSONs although there are some Ids that were generated from the Dialogflow UI.
The question is, can Dialogflow be used like a regular programming language and the somehow package the JSONs into a zip that can be imported. Is the process streamlined somehow with any tool?
Following up on my previous response, these APIs can also be used in creating the agent from scratch as long as you have a GCP project you can link your agent to.
If you're referring to the JSON schema of the exported agent, currently, there’s no JSON schema for the exported agent zip file in the Dialogflow documentation as this is not intended to be edited or replicated. The exported agent zip file is meant to be a backup of your agent for future use. You can use this exported agent to replicate the current agent to a new agent. For restoring and importing agents, you need to upload a zip file which contains the agent.json file as well as the intents or entities folders.
As best practice, it is better to create the agent using Dialogflow APIs if you opt to use JSON files. By following the JSON representation of each type (agent, intents, entities, etc), you will be sure that you are providing the correct and required fields.
Dialogflow has APIs where you can make requests to create and update your agent programmatically. Each Dialogflow edition offers their own API methods.
For Dialogflow Trial and Essentials Edition, you can check the following documentation:
Setup
Dialogflow V2 API reference
Dialogflow V2Beta1 reference
Client Libraries supported
For Dialogflow CX Edition, here are the documentation that will be helpful in creating your agent programmatically:
Setup
Dialogflow CX V3 API reference
Currently available Dialogflow CX client libraries
An android app has been developed by my development team. For which a chatbot is to be developed. So I chose DialogFlow platform to create the chatbot. Here, the API's for the app screens has been created by the development team. For the chatbot in DialogFlow, after creating all the necessary intents, is it just enough to enter the API url in the webhook url section or do I need to apply any logic in inline editor. [Here, the API's are created using python and it is connected with MySql DB]
As a beginner to DialogFlow, I couldn't move forward. Can anyone please help me out. Thanks in advance.
If you made your intents for your chatbot you will still need to write code which chooses what to do for each intent. Dialogflow's documentation can explain you more about the details of what you need to do.
Below is an image of an overview of all components from the documentation. To connect your chatbot to your MySQL API you will have to write a webhook service. This service can be an API which you host somewhere or code that you write in Dialogflows inline editor. Here you can program what API's to call on each intent and how to output it to the user. More info about that can be found here.
I have an exported intents & entities zip file from Dialogflow workspace and tried to import this to IBM Watson workspace its not working is there anyway we could do this ?
Is there any methods we could use to migrate intents from Dialogflow to IBM Watson workspace?
Check out a web app called QBox, it's primary purpose is to benchmark your training data, but it also lets you benechmark against multiple providers. If you run a test by uploading your DialogFlow training data, and select IBM Watson as output, you'll get an option on the resut page to download the training data in IBM Watson format.
Select Watson after you've uploaded your training data:
Run the test, wait a few minutes, and on the results page use the menu on the top right to get your Watson formatted training data:
(Disclaimer: this is a tool I work on, so I have not provided a link, but if you Google the name 'Qbox' along with the term 'chatbot', you should find it!)
DialogFlow is a different product than Watson Assistant. Watson Assistant only allows you to import a workspace that was exported from Watson Assistant (using the export workspace option in the UI) so Assistant is not able to import the dialog from DialogFlow.
You can download Intents and Entities in Watson Assistant in CSV format, see https://console.bluemix.net/docs/services/conversation/intents.html#defining-intents and https://console.bluemix.net/docs/services/conversation/entities.html#defining-entities
You can import entities and intents in a CSV format, but they must be in the specific format that Assistant requires. See the previous 2 links.
There is also this open source project Watson Assistant Workbench (WAW) that allows you to use a few additional formats to create your dialog with Watson Assistant.
Watson Assistant Workbench supports the WA JSON format, custom XML format and even MS XLS format which you can use to define your dialog. Then WAW can process all the data and generate a JSON that can be imported into WA.
This might simplify the conversation process as now you need to "only" convert dialog flow format into WAW XML or XLS (where you for example don't need to work with unique ids of the dialog nodes as in WA JSON format).
So just sharing if this might be interesting - the link to GitHub with Watson Assistant Workbench.
i created a chat bot with dialogflow (V1) and integrated it with google actions for Google Assistant. My company was supported by Google for all development process.
The first release of the chatbot was deployed for all users before 8 may. All works well and the actual release on Google assistant is working well.
The problem now is if i want update the bot with new actions and features the behavior of the chatbot is different in the simulator from draft state to aplha or beta release.
In the webhook the data provided by dialogflow is different (the logs on the cloud function): in the draft all parameters are set correctly , but when switch to alpha or beta version (created from the draft that works well) the parameters are always empty and all the bot answers are wrong.
There are specific actions to make or settings after 8 May to switch from draft to alpha/beta release of Actions on Google to avoid this strange behavior?
Alpha and Beta releases people made last August used to lack the training (machine learning) the agent received. It may be the case here that your alpha and beta versions have the same problem.