I am building my Bot on the Facebook platform, my code is pushed to the Heroku platform and from there the Bot will react to what I have programmed. However, recently I want to add a new intent to my Agent and write code to record action in the intent, and the strange thing is that the Bot doesn't recognize this new intent, but when I try with actions was there before, the bot responded correctly.
I don't know if there is a new Dialogflow policy that I am missing?
MyCode
I had the same problem. I added a new intent to my agent and it did not get recognized. Later I found that it was a language problem. In my code I used the language 'en-US' for my Dialogflow agent, but I added the new intent in the 'en' section.
So, you just need to add your intent in the language you're actually using in your website or application.
Related
My setup:
I'm using actions-on-google to create a custom action for google assistant, every intent is a fallback in dialogflow that is then redirected to my server where I check the intent with a custom nlp engine and then respond to it, using the actions-on-google package.
The issue:
But when an intent is suicidal, for example: "I want to kill myself", google stop the action and give a response instead of letting my custom action handle it. Is there a way to avoid this?, it also happens with certain words like "Save" in that case google stop the action and ask me if I want to save an event or whatnot.
Can I override this behavior?
You're running into a "feature" that Google calls "no-match yielding". In some cases, if you're using a Fallback Intent in Dialogflow, and the Google Assistant itself can handle the question - it will do so.
To avoid this you can use regular Intents that match the #sys.any System Entity.
However, if all you're doing for everything is sending it to your NLU, then you don't need to be using Dialogflow at all. You can just use the Actions on Google v2 to send all TEXT Intents to your NLU for processing.
I have made a query flow in dialogflow and it has four intent and in the last intent it uses a webhook to get data from server side and displays the result. It is trained automatically and works perfectly in dialogflow console returning response and query answer. The issue is it does not work when I use embedded url. It fails to recognize the name intent and asks (Can you repeat again or fallback intent). I've removed all intents and made query again, there is no similar name intents. Yet it works well in console and not in embedded url.
For the webhook part I've used node.js service.
Please help in this issue.
By 'embedded url' if you mean Dialogflow Web Demo (DWD), you should keep in mind that DWD can be used only for simple text messages. It does not support messages from webhook or even rich responses. However, if you steel need a web widget to embed your bot to your webpage you either create your own or you should use third party solutions (like Kommunicate). Here's the link regarding the limitations of DWD.
My Dialogflow knowledge base intent is detected when I ask questions withing the knowledge base document while in the dialogflow console try it now and works well in facebook too. But when integrated kommunicate, if i ask a same question, it defaults to fallback intent and responds with fallback response. What could be the cause. I increased the knowledge base slider to strongest.
Screenshot of the console
Kommunicate supports the knowledgebase feature of Dialogflow. However, This feature is disabled by default because it is in the beta phase.
If you want to enable this feature you can contact to Kommunciate support team at support#kommunicate.io with the knowledgebase Ids and bot Id.
Check this answer to get the knowledgebase id from Dialogflow.
I am completely new to the "Actions on Google" world, but following some tutorials (like this) i have already achieved good results.
My test
With Google Assistant and/or Google Home mini send my commands to a personal nodejs online server.
To do this:
i have created a new project on https://console.actions.google.com/
selected conversational option
selected create action / custom intent option
from Dialogflow i have personalized the Default Welcome Intent and created a new Intent with the Fulfillment option set to Enable webhook call for this intent
And obviously, from Dialogflow > Fulfillment, i have enabled the Webhook option (with the url of my nodejs app), and not the Inline editor.
This procedure works, when my app recognizes my custom intent, the answer is sent to my nodejs app online.
My problem
The procedure works, but i always have to do 2 steps before i can perform my action:
1) Hey Google, talk with "nameofmyapp"
2) Say the command
My goal
Execute my command directly without always having to do this 2 steps.
Absolutely! Google calls this "deep linking". With this, you'll be able to do something like
Hey Google, ask nameof myapp to command
See the documentation for details, but in short you'll
Make sure you have an Intent for the command in Dialogflow, with several possible phrases that can be used to trigger it.
These phrases should be what you'd say under "command" in the example above - you'd omit the "to" part.
Go to the Integrations section in Dialogflow, under the Google Assistant integration.
In the Implicit invocation section, select the Intent that you'd like to allow as a deep-linked Intent.
If the command takes action and then should quit, make sure either you have set this in Dialogflow or your fulfillment calls app.close();
here is the image for better understanding, i merged the inline editor, simulator, and skype
I just created an agent and intent entity with sone parameters and in the fullfilment tab, in the inline editor wrote some code to give response specific to the intent parameter, while all this is working as expected in the simulator. But giving generic response(intent static response) in the Skype integration. Should i do anything extra for skype?
Why is the behaviour different?
Does it have anything to do with webhook?
Ps: I have enabled fullfilment for the intent