Skip to main content

Google Assistant, simpleness of interaction to call a webhook

The creation of an application using Google Assistant is very simple and represent a big impact to interact with users in diverse environments and particularly in home

Hey Google
...Where is my dog?

If we plan to connect a security camera system, the challenge of finding my pet in an automated way is more feasible, then I will give more details of how I intend to do it. Now we are going to prepare the functionality of the assistant’s requests.


To create an agent and interact with Google Assistant, we will use DialogFlow.


Let's see the main elements to create an agent, and using this agent call a webhook with some functionality. * Part of the objective will be to try to prepare the logic of interaction with a home security system

*Arlo System

From the DialogFlow console, we will create a new agent:
We can customize different support languages, for this case I will use English to facilitate the testing of the agent. [You can include Spanish and also go in depth using the sub-versions like es-419 - latin]


Now we will create an intent where we will represent the concept of action to be performed by the agent and the reactions that the agent will have.

Pay special attention to completing the phrases that the user should use to trigger actions on the agent.


This is the json representation of the intent:


I also share the phrases used to understand the user. ¨User Says¨:

Then we can add a name to the action, this is important to add logic to this action into the code implementation.

Finally, an important part of these operations is the interaction with webhooks. Here we can connect different services. For this example, the webhook will manipulate a system of security cameras following commands to make a user's utility simpler and more flexible.


ArloCamService is a sample project that provides support to a webhook for Google Assistant.

Our complete implementation architecture plan:

Actions of Google Assistant propose interesting utilities and simplicity of development, in addition it's provide a great option for developers to innovate into the topic/environment of interaction with the user using the simplicity of the dialogue interaction.

Creative Commons License
Google Assistant, simpleness of interaction to call a webhook by Nicolas Bortolotti is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Comments

Popular posts from this blog

SMI Developer Day - Session 2 was pure developers adrenaline

A new session of SMI Developer Day program has been conducted at the Cultural Center Borges in Buenos Aires. The event was pure adrenaline to the ecosystem of technology development in Google. A great attendance and I could feel pure adrenaline at the conference on May 8 at the Cultural Center Borges in the context of SMI Developer Day event . In this opportunity we present an approach to development Web solutions , innovative technologies such as HTML5 and present an option for persistence in disconnected scenarios. A great conversation environments with a lot of questions, showed the state of motivation of the developer community in the region. A region full of talent. A region that every day becomes more involved in technology , mobility , computing in the cloud. Furthermore, this region strengthens a vision of entrepreneurship, and drive an amazing ecosystem. An excellent shared moment with the community ...

Model Top-Down Analysis in software products.

In this paper will discuss an approach from the environmental variability of presentation software solutions. Focusing on the concept of software product family. If we play the role of architects:           How many times we try analyzing common feature in different forms of presentation?           How many times have we requested a mobile solution attached to our traditional solution?           Are simply the decisions to implement new presentations of the software solution? Here is an introduction to the concept…. Software organizations are building a product vision characterized by the development and evolution of product families instead of creating a specific software product for a given client. This trend is driven by several factors such as, business strategy, diversity computing devices and reuse of software components in complex software systems. Howeve...