Google Assistant (Conversational)

Integration published by Jovo | 5,815 downloads

Build Conversational Actions for Google's Assistant platform

User Data

Learn more about how to get access to Google Action user information.

Introduction

User information is mainly used to offer a more personalized experience, but you can't access it right away. First you have to ask for permission.

User ID

With Jovo, a Google Action userId is created by generating a random id using uuidv4, and then saving it to the user storage object.

Note: User Storage only works for Google Assistant users who are verified. For users that are not verified, the data will expire at the end of the conversation. Learn more in the official Google Docs.

Google Profile

Since Google does not provide a way to get user information such as email and name yet, you need to use the Google profile to access their data.

This will return an object containing user information in the following format:

In order to get access to the user profile, you'll need the user to link their account to access their information, if the user is not already linked.

Account Linking

To implement Account Linking in your voice application, we recommend using scenes to handle the individual steps of account linking.

There are multiple ways of setting up the scenes necessary, we recommend creating them inside your model file to deploy them directly to the Google Conversational Actions Console.

These two scenes, located inside your Jovo model, determine how Account Linking is handled for your Conversational Action.

AccountLinkingScene propagates the request to AccountLinkingScene_AccountLinking, depending on whether the user is verified or not, which in turn sends the result from the Account Linking process to your webhook handler.

To trigger Account Linking, you can instruct your Google Action to handle the next conversation step with the specified scene:

After the user has responded to your account linking request, you will receive a request to notify you about the result, which will be mapped to the Jovo built-in ON_SIGN_IN intent:

Example Javascript | Example Typescript

Google Assistant Changelog

Current version might be higher than the latest changes displayed below because of updates of dependencies.

2021-07-07 [3.5.4]
  • #948 ✨ Add enableFullScreen and continueTtsDuringTouch (@aswetlow)

2021-02-22 [3.5]

  • #901 Move setResponse from response to after.response middleware (@aswetlow)
  • #901 Fix missing unit test methods in ConversationalResponse (@aswetlow)
2021-02-04 [3.4.0]
  • #892 ✨ Transactions for Google Assistant Conversational Actions (@aswetlow)
2021-01-28 [3.3.2]
  • #890 ✨ Add Conversational Actions functionality to Jovo Debugger (@aswetlow)
2020-12-03 [3.3.0]
  • #871 Add missing and broken Google Conversational Action features (@aswetlow)
2020-11-20 [3.2.4]
2020-11-16 [3.2.3]
  • Adds Interactive Canvas to Google Conversational Actions (@aswetlow)
2020-11-10 [3.2.2]
  • #856 Fixes several Google Conversational Actions issues (@aswetlow)
2020-11-05 [3.2.1]

Fix missing locale in push notifications object

2020-09-29 [3.1.3]
  • #831 :recycle: Enhance Google AssisConversational Actions (@maswetlow)

2020-09-29 [3.1.0-alpha.0]

  • #829 ✨ Work In Progress: Google Assistant Conversational Actions (@aswetlow)

Join Our Newsletter

Be the first to get our free tutorials, courses, and other resources for voice app developers.