actions-on-google

Google Assistant location permissions not stored between requests

放肆的年华 提交于 2019-11-27 16:32:48
问题 With API.AI and the Google Assistant, I'm requesting permission to get the user's name and location. The intent is that I'll be able to ask for permission once, and subsequent requests to my Action will not need to ask again (since this will make for a very stilted conversation every time the user talks to my Action). What I am finding is that I'm only getting the information in the intent tied to the actions_intent_PERMISSION - the information isn't sent in other intent fulfillments, even if

Get email from user using Google actions

时间秒杀一切 提交于 2019-11-27 15:21:42
问题 I want to recieve the user email using Google Actions as documented here but docs talks about EMAIL permission, but when I read the permission docs here I can't find any EMAIL permission. Any help? How can I receive the user email? 回答1: Ya, unfortunately the Assistant's SDK doesn't give you the email address. But if you implement account linking (like Ahmed mentioned) and use the Streamlined Flows, then you'll be getting the email provided to you; you just need to use the jsonwebtoken library

Dialogflow NodeJs Fulfillment V2 - webhook method call ends before completing callback

生来就可爱ヽ(ⅴ<●) 提交于 2019-11-27 08:48:08
问题 I am developing a Dialogflow webhook using dialogflow-fulfillment-nodejs client to find temperature for a city. While using the services to fetch the temperature for a city, everything works and the correct response is also generated but the response is not sent to the user even when the right method is called. Here is the issue in the Dialogflow GitHub repo Code function getTemp(agent) { const timeStart = new Date().getTime(); console.info(`temp function called`); // agent.add(`Temperature

How to make asynchronous calls from external services to actions on google?

随声附和 提交于 2019-11-27 08:38:07
问题 I'm trying to connect Google Home to an external chatbot with actionssdk. I have an API that take user inputs and send them to my chatbot with webhook, but my chatbot make a response calling another endpoint of my API in an async way, and I can't show the response in actions on Google or Google Home. I create an actionssdkApp. const { actionssdk, SimpleResponse, Image, } = require('actions-on-google'); var app = actionssdk(); var express_app = express(); My API has 2 endpoints. One of them is

Make google actions development project preview persist longer

本秂侑毒 提交于 2019-11-27 04:13:06
问题 I want to make google voice actions app for my Google Home. But, based on quick research, as of Dec 11, google does not allow private projects for Google Home. References: Can I develop a private action only accessible via my google home or linked account? How can I run my development action on my Google Home? I understand that I can preview the app from API.ai project, and it deployes to the linked Google Home device. But the issue is, the deployed app does not persist. It is no longer

How can I tell Actions on Google to stream audio?

走远了吗. 提交于 2019-11-27 02:14:39
问题 I am writing an app to work with Google Actions. The only bummer is that I can't find any information about how to form my response so that Google will stream audio from a given URL. Does Google even support this yet? I have written the same app on Alexa already, and on Alexa all you have to do is Return an audio item (token, URL, play command) and Alexa will start streaming it. I should mention that I am NOT using API.AI, but am simply using the Actions SDK and am hosting my web service on

How do I save and retrieve information across invocations of my agent in Dialogflow?

雨燕双飞 提交于 2019-11-27 02:02:48
问题 I would like my Actions on Google agent to store and retrieve certain pieces of information across invocations - like a cookie. How do I do this? 回答1: You have a lot of options on how you want to do this, depending on exactly what you're trying to do. It isn't exactly like a web cookie, although there are similarities. If you want the equivalent of a session cookie, information that is retained during a single conversation , then your options are Using the Session ID provided as part of the

Google Home Authorization Code and Authentication with Google Account

被刻印的时光 ゝ 提交于 2019-11-26 19:09:19
I am currently attempting to authenticate a Google account with a Google Home Action and retrieve the Authorization Code from the credentials. I do not want the access token, but the authorization code . I have looked at this post and discovered that Google has updated their policy and no longer allow their own OAuth endpoints to be used for the account linking authorization code flow: When implementing account linking using OAuth, you must own your OAuth endpoint That being said, What is the correct way to authenticate an existing Google user with my Action and the necessary scopes? (I need

How to authenticate user with just a Google account on Actions on Google?

ⅰ亾dé卋堺 提交于 2019-11-26 08:03:30
Currently Google Assitant includes an easy way to request non-identifiable information about the user and a detailed flow to authenticate the user on a third party service through OAuth2. What about if all I need is have the user authenticate on Google itself? I tried filling in the account linking flow using Google OAuth2 information, but that seems not to work. If that last thing is supposed to work fluently than that would be enough of an answer. Context: Users already authenticate only with Google on a related webpage. All I need is to link this already authenticated account with the less

How to authenticate user with just a Google account on Actions on Google?

流过昼夜 提交于 2019-11-26 01:16:26
问题 Currently Google Assitant includes an easy way to request non-identifiable information about the user and a detailed flow to authenticate the user on a third party service through OAuth2. What about if all I need is have the user authenticate on Google itself? I tried filling in the account linking flow using Google OAuth2 information, but that seems not to work. If that last thing is supposed to work fluently than that would be enough of an answer. Context: Users already authenticate only