how to use match action name of intent of Dialogflow to handler in new SDK v2?
See original GitHub issueI’m migrating from SDK v1 to v2. And found that new SDK doesn’t catch Dialogflow action names.
app.intent('action-name', handler);
Doesn’t work.
I can match manually action name to handle in fallback
handler, but maybe it could be fixed in SDK?
And what is the plan for Dialogflow action
name, is it deprecated and shouldn’t be used anymore?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Build fulfillment (Dialogflow) - Google Developers
Click the + sign by the Intents menu item in Dialogflow's left navigation. The Intent Editor appears where you can enter the following...
Read more >Intents | Dialogflow ES - Google Cloud
When an intent is matched, Dialogflow provides the action to your system, and you can use the action to ... Agent and intent...
Read more >27 The Dialog Flow Definition - Digital Assistant
OBotML uses a simple syntax for setting variables and defining states. Because it's a variant of YAML, keep the YAML spacing conventions in...
Read more >IntentsGrpc (java API) - Google APIs
When you pass user input to the [DetectIntent][google.cloud.dialogflow.v2. ... **Events** - allow for matching an intent by using an event name instead of ......
Read more >Handling Permissions with DialogFlow and Actions On Google
Create an intent that will be triggered by DialogFlow and whose role is to send an action to your application. · In your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Same here - this makes migrating to the new version much more complicated and error-prone.
I posted my proposal to add a new method
app.action
so that developers can register my handler function with an action name as #164.