How can we Unlink the google account from the particular intent in inline code?
There are no built-in actions to trigger sign out like there are for sign in (actions_intent_SIGN_IN).
Suppose user by mistaken logged in via some another account and now he wants to switch. How we can provide this facility?
Currently it is not possible to unlink the Account via Voice. But the user can reset the Account at the Action Directory on the bottom of the side.
Related
I am currently working on a nest JS project that leverages the google node package to delete an event from a users calendar (gcal). Gcal successfully deletes the meeting, but the deletion notification to attendees comes from the administration account the api uses to connect.
Is there a way to alias the notification that is sent out to attendees so it looks like the owner of the calendar sent out the notification, not the google api administrator?
node package
https://www.npmjs.com/package/google
google api delete docs
https://googleapis.dev/nodejs/googleapis/latest/calendar/classes/Resource$Events.html#delete
This is the code snippet
// https://googleapis.dev/nodejs/googleapis/latest/calendar/classes/Resource$Events.html#delete
await this.calendar.events.delete({
calendarId,
eventId,
sendNotifications: true,
sendUpdates: 'all',
});
Google Calendar will trigger the respective notifications based on the authenticated actor.
In your scenario, that will be "administration account the api uses to connect".
If you are using this automation script in a Workspace Environment, you may want to impersonate another user (like the event organizer for example) to delete the event.
To achieve that in a Workspace scenario, you will need Domain-Wide Delegation of Authority set up.
NOTE: Make sure the authenticated user (and/or the actor of the delete call) has enough permissions over the affected event in order to delete it or use an account with Calendar Admin role (or Super Admin).
Why when I want to try an Dialogflow's intent in Google Assistant, I get the message "Permission denied for your request"?
I just ran into this problem. Your first step may be to make sure that you are using the same account (i.e. gmail account) on Dialogflow that you used to make your project on your Actions Consoles
I am signed into multiple gmail accounts and only noticed that my Actions Console was signed into one account and my Dialogflow was signed into a different account. When I made sure both Actions Console and Dialogflow were signed into the same account, I was able to run my test.
In google dialogflow using node js , i have used the account linking feature to store user data into the database. After the signin intent, i want to trigger welcome intent or any other intent. Now its getting signed in and nothing happens after that.How to trigger the next intent without getting response from the user? Now its getting signed in and nothing happens after that. What am i doing wrong?
If you wish to continue the conversation after a sign-in has been completed have a look at the sign-in helper. This will allows you to create an intent with the event for sign-in and it will allow you to continue the conversation.
If you handover from a speaker to a phone your conversation will always end, the user will have to sign-in and restart the conversation if you use that.
I'm building an application using Accountlinking for a Google Home speaker using the Actions On Google SDK. I am using the Oauth feature which allows a user to sign-in into an account on their phone by sending them a link with a login window.
When the sign-in is triggered, the conversation on the Google speaker is ended. I would like to use some user information that comes from the accountlinking process right after the user is done with the accountlinking.
When you build a conversation for assistant on mobile, you can await the actions.intent.SIGN_IN event to continue the conversation, but even when you implement this, a conversation for the speaker will end.
Is there any way to use user information directly after a user linked
their account for a Google Home speaker app without users having to restart the conversation?
Once the user has to jump to the phone to perform account linking, the conversation on the speaker ends since the context has shifted devices. After account linking finishes, you could try to transfer to a new surface, although you will not necessarily have the ability to go back to the original device.
This is a basic functionality of subscription so I must be missing something!
How can I programmaticaly cancel a Google Wallet subscription? Obviously when the user cancels their account with our service we need to cancel their subscription, instead of having to ask them to go to their Google Wallet console and cancel it themselves or us having to do it manually for every cancellation from our console?
[EDIT] Just to clarify, the question is about Google Wallet subscriptions (digital goods)
See above note, as I understand the only way for a cancellation of payment is a manual one, so when a user cancels our service they either have to go and cancel the payment themselves, or for us to do it manually.
Users can view the status of all of their subscriptions and cancel them if necessary from the My Apps screen in the Play Store app. Currently, the In-app Billing API does not provide support for programatically canceling subscriptions from inside the purchasing app.
More details can be found at Subscription Cancellation