You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really enjoy testing with Virtual Alexa and have recently begun some work with Google Actions using Actions Builder and was hoping to do the same kind of testing for the actions I develop. I turned to Virtual Google Assistant and, unless I'm missing something, cannot use it for actions created with Actions Builder.
I could be misreading the situation, but it appears that Google is promoting Actions Builder as the successor to Dialogflow. Indeed, it is a much easier way to develop actions and I prefer it over Dialogflow. Therefore, it would make sense for Virtual Google Assistant (or some separate testing framework) to support Actions Builder.
The text was updated successfully, but these errors were encountered:
Hi Craig,
We do not have current plans to add support for the Actions Builder. We are still doing bug fixes on these projects, but we do not have any plans for major new development for them at this time.
If this changes, we will let you know.
Best,
John
*John Kelvie*
Co-Founder & CEO | 202-251-7107
Bespoken ( https://bespoken.io/ ) - Testing, Training and Monitoring for Voice and Chat
On Mon, Jan 17, 2022 at 2:09 PM, Craig Walls < ***@***.*** > wrote:
As of today it has been 19 months since Google Actions Builder was
announced ( https:/ / developers. googleblog. com/ 2020/ 06/ announcing-actions-builder-actions-sdk.
html (
https://developers.googleblog.com/2020/06/announcing-actions-builder-actions-sdk.html
) ). As far as I can tell, Virtual Google Assistant still only works with
DialogFlow (specifically, because configuration requires a reference to
the agent).
I really enjoy testing with Virtual Alexa and have recently begun some
work with Google Actions using Actions Builder and was hoping to do the
same kind of testing for the actions I develop. I turned to Virtual Google
Assistant and, unless I'm missing something, cannot use it for actions
created with Actions Builder.
I could be misreading the situation, but it appears that Google is
promoting Actions Builder as the successor to Dialogflow. Indeed, it is a
much easier way to develop actions and I prefer it over Dialogflow.
Therefore, it would make sense for Virtual Google Assistant (or some
separate testing framework) to support Actions Builder.
—
Reply to this email directly, view it on GitHub (
#63 ) , or unsubscribe
(
https://github.com/notifications/unsubscribe-auth/ABJV6ILV5GH4B4AVLI6SL5DUWRSNPANCNFSM5MFMYHHA
).
You are receiving this because you are subscribed to this thread. Message
ID: <bespoken/virtual-google-assistant/issues/63 @ github. com>
As of today it has been 19 months since Google Actions Builder was announced (https://developers.googleblog.com/2020/06/announcing-actions-builder-actions-sdk.html). As far as I can tell, Virtual Google Assistant still only works with DialogFlow (specifically, because configuration requires a reference to the dialog flow folder).
I really enjoy testing with Virtual Alexa and have recently begun some work with Google Actions using Actions Builder and was hoping to do the same kind of testing for the actions I develop. I turned to Virtual Google Assistant and, unless I'm missing something, cannot use it for actions created with Actions Builder.
I could be misreading the situation, but it appears that Google is promoting Actions Builder as the successor to Dialogflow. Indeed, it is a much easier way to develop actions and I prefer it over Dialogflow. Therefore, it would make sense for Virtual Google Assistant (or some separate testing framework) to support Actions Builder.
The text was updated successfully, but these errors were encountered: