Google Assistant - existing dialogflow intents & new actions cooperation

42 views
Skip to first unread message

W R

unread,
Mar 15, 2021, 11:00:20 AM3/15/21
to Dialogflow Essentials Edition users
Hi,

I have a technical question about the Google Assistant - unfortunately, I couldn't find a clear answer anywhere.

At the moment our company have:
1. the conversational chatbot built on Dialogflow, which is constantly developed by our employees
2. Google Actions agent. Our developers managed to construct the connection of the Google account and our client's account on our platform using OAuth 2.0 and created the first actions that, by the exchange of tokens, allow the return of certain information from our platform to the Google Assistant and vice versa - providing certain information in the Google Assistant that are sent and saved in the customer's account on our platform.

We would like both actions on actions.google.com (2) and conversations on Dialogflow (1) to cooperate with each other in the Google Assistant. One team is working on the chatbot, and the other on advanced actions, and we would like it to stay that way.

My question is - is the absolute only way to finally publish it on the google assistant is to migrate the chatbot from Dialogflow to Actions Builder and stop using Dialogflow?
Or maybe there is a simpler solution where both these environments (of course woring on one profile / agent) cooperate with each other and it will be possible to continue working on dialogflow?
We understand the advantages of Action Builder, but Dialogflow is just good enough for our needs.

I will be very grateful if anyone can help. :)

swaylan

unread,
Mar 17, 2021, 11:58:22 AM3/17/21
to Dialogflow Essentials Edition users
Hello,

As per our public documentation [1], the preferred, fully supported way, and easy way to publish chatbots from Dialogflow to Google Assistant is via the "Dialogflow to Actions Builder migration tool", as Actions Builder backend and frontend has been specifically designed to create a more seamless interaction between both products, but doesn't integrate with Dialogflow as you've noted. There are a number of benefits to do it this way, located here [2].

Now, it is still possible to not migrate in hopes of continually developing using Dialogflow and publishing to Google Assistant, using the legacy integration functionality of Dialogflow (ES), called Conversational Actions. More detailed information is located [3], [4], and [5].

Here are 2 instructional articles that provide step-by-step instructions, as well as real-world examples [6][7].

I hope this information helps to clarify your options.

Reply all
Reply to author
Forward
0 new messages