Actions on google console

Actions on google console DEFAULT

Google Assistant

The integration allows you to control things via Google Assistant on your mobile, tablet or Google Home device.

Automatic setup via Home Assistant Cloud

With Home Assistant Cloud, you can connect your Home Assistant instance in a few simple clicks to Google Assistant. With Home Assistant Cloud you don’t have to deal with dynamic DNS, SSL certificates or opening ports on your router. Just log in via the user interface and a secure connection with the cloud will be established. Home Assistant Cloud requires a paid subscription after a 30-day free trial.

For Home Assistant Cloud Users, documentation can be found here.

Manual setup

The Google Assistant integration (without Home Assistant Cloud) requires a bit more setup than most due to the way Google requires Assistant Apps to be set up.

To use Google Assistant, your Home Assistant configuration has to be externally accessible with a hostname and SSL certificate. If you haven’t already configured that, you should do so before continuing. If you make DNS changes to accomplish this, please ensure you have allowed up to the full 48 hours for DNS changes to propagate, otherwise, Google may not be able to reach your server. Once you have confirmed you can reach your Home Assistant from outside your home network, you can set up the Google integration:

Google Cloud Platform configuration

  1. Create a new project in the Actions on Google console.

    1. Click and give your project a name.
    2. Click on the card, then click the button.
    3. Click under to give your Action a name - Home Assistant will appear in the Google Home app as
    4. Click on the tab at the top of the page to go back.
    5. Click , then click .
    6. Add your Home Assistant URL: in the box, replace the with the domain / IP address and the port under which your Home Assistant is reachable.
    7. Click .
    8. Click the three little dots (more) icon in the upper right corner, select
    9. Make note of the that are listed on the tab of the page.
  2. is required for your app to interact with Home Assistant.

    1. Start by going back to the tab.
    2. Click on under the section of the page.
    3. If asked, leave options as they default and select .
    4. Then if asked, for the select and . Click
    5. Enter the following:
      1. Client ID: . (Replace with your project ID from above)
      2. Client Secret: Anything you like, Home Assistant doesn’t need this field.
      3. Authorization URL: . (Replace with your values.)
      4. Token URL (replace with your actual URL): . (Replace with your values.) Click , then again.
    6. In the textbox, type and click , then type and click again.
    7. Do NOT check .
    8. Click , then click
    Screenshot: Account linking
  3. Select the tab at the top of the page, then in the upper right hand corner select the button to generate the draft version Test App. If you don’t see this option, go to the tab instead, click on the button in the top right below the header, and ensure is enabled (if it isn’t, enable it).

  4. Add the integration configuration to your file and restart Home Assistant following the configuration guide below.

  5. Add services in the Google Home App (Note that app versions may be slightly different.)

    1. Open the Google Home app.
    2. Click the button on the top left corner, click , in the “Set up a device” screen click “Works with Google”. You should have listed under ‘Add new’. Selecting that should lead you to a browser to login your Home Assistant instance, then redirect back to a screen where you can set rooms and nicknames for your devices if you wish.

If you’ve added Home Assistant to your phone’s home screen, you have to first remove it from home screen, otherwise, this HTML5 app will show up instead of a browser. Using it would prevent Home Assistant redirecting back to the Google Home app.

Allow Other Users

If you want to allow other household users to control the devices:

  1. Open the project you created in the Actions on Google console.
  2. Click on the top of the page, then click located to the page left, then click the three little dots (more) icon in the upper right corner of the console.
  3. Click Manage user access. This redirects you to the Google Cloud Platform IAM permissions page.
  4. Click ADD at the top of the page.
    1. Enter the email address of the user you want to add.
    2. Click Select a role and choose Project < Viewer.
    3. Click SAVE
    4. Copy and share the Actions project link () with the new user.
  5. Have the new user open the link with their own Google account, agree to the Terms of Service popup, then select “Start Testing”, select VERSION - Draft in the dropdown, and click “Done”.
  6. Have the new user go to their app to add to their account.

Enable Device Sync

If you want to support active reporting of state to Google’s server (configuration option ) and synchronize Home Assistant devices with the Google Home app ( service), you will need to create a service account. It is recommended to set up this configuration key as it also allows the usage of the following command, “Ok Google, sync my devices”. Once you have set up this component, you will need to call this service (or command) each time you add a new device in Home Assistant that you wish to control via the Google Assistant integration. This allows you to update devices without unlinking and relinking an account (see below).

  1. Service Account
    1. In the Google Cloud Platform Console, go to the Create Service account key page.
    2. At the top left of the page next to “Google Cloud Platform” logo, select your project created in the Actions on Google console. Confirm this by reviewing the project ID and it ensure it matches.
    3. From the Service account list, select .
    4. In the Service account name field, enter a name.
    5. In the Service account ID field, enter an ID.
    6. From the Role list, select > .
    7. Click and then . You are returned to the service account list, and your new account is shown.
    8. Click the three dots menu under next to your new account, and click . You are taken to a page.
    9. Click then . Leave the as and click . A JSON file that contains your key downloads to your computer.
    10. Use the information in this file or the file directly to add to the key in the configuration.
    11. Click .
  2. HomeGraph API
    1. Go to the Google API Console.
    2. At the top left of the page next to “Google Cloud Platform” logo, select your project created in the Actions on Google console. Confirm this by reviewing the project ID and it ensure it matches.
    3. Click Enable HomeGraph API.
  3. Try “OK Google, sync my devices” - the Google Home app should import your exposed Home Assistant devices and prompt you to assign them to rooms.

YAML Configuration

Now add your setup to your file, such as:

Configuration Variables

Looking for your configuration file?

project_id stringRequired

Project ID from the Actions on Google console (looks like )

secure_devices_pin string (Optional)

Pin code to say when you want to interact with a secure device.

service_account mapRequired

Service account information. You can use an include statement with your downloaded JSON file, enter data here directly or use secrets file to populate.

private_key stringRequired

Private key in PEM format

client_email stringRequired

report_state boolean (Optional, default: false)

Actively report state changes on entities. This speeds up response time for actions affecting multiple entities since Google Assistant knows pre-hand what state they are. It is also required for some features on visual controls.

expose_by_default boolean (Optional, default: true)

Expose devices in all supported domains by default. If domains is set, only these domains are exposed by default. If is set to false, devices have to be manually exposed in .

exposed_domains list (Optional)

List of entity domains to expose to Google Assistant if is set to true. This has no effect if is set to false.

entity_config map (Optional)

Entity specific configuration for Google Assistant

YOUR_ENTITY_ID map (Optional)

name string (Optional)

Name of the entity to show in Google Assistant

expose boolean (Optional, default: true)

Force an entity to be exposed/excluded.

aliases list (Optional)

Aliases that can also be used to refer to this entity

room string (Optional)

Allows for associating this device to a Room in Google Assistant.

Available domains

Currently, the following domains are available to be used with Google Assistant, listed with their default types:

  • alarm_control_panel (arm/disarm)
  • camera (streaming, requires compatible camera)
  • group (on/off)
  • input_boolean (on/off)
  • input_select (option/setting/mode/value)
  • scene (on)
  • script (on)
  • switch (on/off)
  • fan (on/off/speed percentage/preset mode)
  • light (on/off/brightness/rgb color/color temp)
  • lock
  • cover (on/off/set position)
  • media_player (on/off/set volume (via set volume)/source (via set input source)/control playback)
  • climate (temperature setting, hvac_mode)
  • vacuum (dock/start/stop/pause)
  • sensor (temperature setting for temperature sensors and humidity setting for humidity sensors)
  • humidifier (humidity setting/on/off/mode)

Some of these devices may not display correctly in the Google Home app, such as media_player, however voice commands will still work.

Secure Devices

Certain devices are considered secure, including anything in the domain, domain and with device types , or .

By default these cannot be opened by Google Assistant unless a is set up. To allow opening, set the to something and you will be prompted to speak the pin when opening the device. Closing or locking these devices does not require a pin.

For the Alarm Control Panel if a code is set it must be the same as the . If is set to the system will arm without prompting for the pin.

Room/Area support

Entities that have not been explicitly assigned to rooms but have been placed in Home Assistant areas will return room hints to Google with the devices in those areas.

Climate Operation Modes

There is not an exact 1-1 match between Home Assistant and Google Assistant for the available operation modes. Here are the modes that are currently available:

  • off
  • heat
  • cool
  • heatcool (auto)
  • fan-only
  • dry
  • eco

TV Channels

There is no TV channel object in Home Assistant. TV channel can only be changed by number, not by name (for example, ).


404 errors on request sync

Syncing may fail after a period of time, likely around 30 days, due to the fact that your Actions on Google app is technically in testing mode and has never been published. Eventually, it seems that the test expires. Control of devices will continue to work but syncing may not. If you say “Ok Google, sync my devices” and get the response “Unable to sync Home Assistant” (or whatever you named your project), this can usually be resolved by going back to your test app in the Actions on Google console and clicking under . Regenerate the draft version Test App and try asking Google to sync your devices again. If regenerating the draft does not work, go back to the section and just hit the key for the URL to recreate the Preview.

The service requires that the initial sync from Google includes the . If not, the service will log an error that reads something like “Request contains an invalid argument”. If this happens, then unlink the account from Home Control and relink.

The service may fail with a 404 if the of the HomeGraph API differs from the of the Actions SDK found in the preferences of your project on Actions on Google console. Resolve this by:

  1. Removing your project from the Google Cloud API Console.
  2. Add a new project to the Actions on Google console Here you get a new .
  3. Run through the previously mentioned [Actions on Google console] setup instructions until the step to create a .
  4. Once you begin to create a new in the [Google Cloud API Console], ensure you select the project created in [Actions on Google console] by verifying the .
  5. Enable HomeGraph API to the new project.

Verify that the Google Assistant is available on If it is working it should return when opened in a browser or via curl.

403 errors on request sync

The service may fail with a 403 if the HomeGraph API is not enabled. Go to Google API Console and verify that HomeGraph API is enabled for your project.

404 errors on report state

If you receive 404 errors linked to reporting state in your log, Home Assistant is reporting state for entities that were never synced to Google. Ask your Google Home to or run the service .

Error during linking: “Could not update the setting. Please check your connection”

Your fulfillment URL may be invalid or unreachable. Recheck the as specified in Manual Setup and verify that it’s publicly reachable.


When using NGINX, ensure that your line does not have a trailing , as this will result in errors. Your line should look like:

Unlink and relink

If you’re having trouble with Account linking failed after you unlinked your service, try clearing the browser history and cache.

Failed linking - Could not update the setting. Please check your connection

If you’re having trouble linking your account, with the error message after logging into your Home Assistant instance, try setting then exposing a single simple device (light or switch preferably). It is also worth checking if any home ad blocker is disabled if you are having issues.


Build your own Action for Google Assistant

Luckily you don’t have to wait for someone to implement this missing feature. You can do it yourself! Google has an entire platform dedicated to helping you extend the functionality of the Google Assistant, by defining custom actions.

Compared to other Google products and services, the Google Assistant platform still feels relatively new, and unlike the crowded mobile app scene, there’s still lots of opportunities to create Actions that feel completely different to everything else currently on the market. If you take a look at the Google Assistant Actions directory, you’ll find some interesting Actions third parties have developed for Assistant and Google Home, but it’s far from an exhaustive list!

Read Next:Actions on Google makes it easy to build apps for Google Assistant 

Let’s look at how to build a complete Google Assistant Action. By the end of this article, you’ll have created an Action that asks the user various questions, parses their responses, and then extracts specific pieces of information, which it then uses to personalize the conversation and drive it forward.

What we’re going to build

We’ll be building a bad joke generator action that learns the user’s name, and finds out whether they want to hear a cheesy joke about dogs or cats.

When designing an Action, it’s a good idea to map out all the different routes the conversation can take, so here’s what we’ll be building:

Creating an Actions project and a Dialogflow agent

Every single Action requires the following:

  • An Actions project- This is where you’ll manage, test and publish your Action, and perform admin tasks like guiding your Action through the publication process.
  • A Dialogflow agent- This is a web-based service you’ll use to integrate your Action with the Google Assistant. You’ll use this agent to define how users interact with your Action, the parameters Dialogflow should extract, and how the conversation should progress.

To create these components:

  • Head over to the Actions on Google Developer Console and log in with your Google account. If this is your first visit, then follow the instructions to create an Actions on Google account.
  • When prompted, select Add/import project.
  • Give the project a name; I’m using “BadJokeGenerator.”
  • Click Create Project.
  • Rather than pick a category, select Skip.
  • In the Console’s left-hand menu, select Actions.
  • Select Add your first action.
  • Choose the language(s) in which your Actions directory listing should be displayed. Click Update.
  • Select Custom intent, followed by Build.
  • The Dialogflow Console will launch in a new tab. Review this information, and if you’re happy to proceed, then create your Dialogflow agent by clicking Create.

Welcome the user to your Action

Every conversation has to start somewhere! Whenever you create a Dialogflow agent, a Welcome intent is generated automatically, which represents the entry point into your Action.

You define how your Action responds to user input via Dialogflow intents. It can respond in two ways:

  • Static. If your Action always responds in the same way, you can provide a canned response as plain text.
  • Dynamic. You can use a webhook, also known as a fulfilment, to figure out the relevant response and send it back to the Google Assistant, and ultimately to the user.

Your responses should guide the user on what to say next, so I’m going to welcome the user to our application, and then ask for their name. Since this is a static response, we can supply it as plain text:

  • Select Intents from the Console’s left-hand menu.
  • Position your cursor over the Default Welcome intent text, and give it a click. This launches Dialogflow’s intent editor.
  • Scroll to the editor’s Response section.
  • Delete all the pre-populated stock responses, by hovering over each response and then clicking the Trash icon.
  • Click the Add responses button, and select Text response.
  • Enter this message: “Hi, welcome to Bad Joke Generator. What’s your name?”
  • Click Save.

Language training: Define your conversation’s grammar

Next, we need to make sure our Dialogflow agent can identify which part of the user’s response is the required name parameter. This means providing examples of all the different ways that someone might provide their name.

When it comes to understanding and processing language, Dialogflow’s natural learning understanding (NLU) engine does a lot of the heavy lifting, so you don’t have to list every potential response. However, the more training phrases you provide, the greater your chances of a successful match, so try to be as thorough as possible.

To train your agent:

  • In the Console’s left-hand menu, select the little + that appears alongside Intents.
  • At the very top of your screen, give this intent the title create_name.
  • Click to expand the Actions and parameters section.
  • In the Parameter name section, enter “name.”
  • Next, we need to define an entity, which will be responsible for extracting parameter values from the user input. Dialogflow has a pre-defined “name” entity you can use, so start typing @sys.given-name, and then select it from the subsequent dropdown when it appears.
  • Make sure the conversation doesn’t progress until Dialogflow has learned the user’s name, by selecting Required.
  • Click Define prompts and provide a few follow-up phrases for the Assistant to repeat until it gets the necessary information, such as “Sorry, I didn’t quite catch your name! Can you repeat it?” If at any point the user gives an unexpected response, our Action will cycle through these prompts, until it manages to extract the correct parameter.
  • When you’re happy with the phrases you’ve entered, click Close.
  • Click to expand the Training phrases section.
  • In the Add user expression field, enter “My name is John” and then press the Enter key.

By default, Dialogflow should recognize “John” as the required parameter, and assign it to the @sys.given-name entity.

Repeat this process for variations on this phrase, such as “John is my name,” “I’m called John,” and “John Smith.”

If Dialogflow ever fails to assign @sys.given-name to “John,” then you can create this assignment manually:

  • Highlight the word “John.”
  • Select @sys.given-name:name from the dropdown.

Create and deploy your webhook

Now that our agent can recognize the name parameter, let’s put this information to good use! You can address the user by name, by creating a Dialogflow webhook:

  • Still in the intent editor, click to expand the Fulfilment section.
  • Select Enable fulfilment.
  • Drag the Enable webhook call for this intent slider to the On position.
  • Save your changes, by scrolling to the top of the screen and then clicking Save.

Next, create the webhook using Dialogflow’s Inline Editor:

  • Select Fulfilment from the Console’s left-hand menu.
  • Push the Inline Editor slider to the On position.
  • Make sure the index.js tab is selected, and then copy/paste the following:


  • Deploy your webhook, by clicking the Deploy button. Dialogflow will now provision and deploy your webhook code on a managed environment, using Cloud Functions for Firebase. This may take a few minutes, depending on the speed of your Internet connection.

In the above code, “name” refers to the parameter we defined in the intent editor.

Test your Action

You can put your project to the test, using the Actions Simulator:

  • Make sure you’ve enabled the necessary permissions, by heading to the Activity controls page and checking that the Web & App Activity, Device Information and Voice & Audio Activity sliders are all set to On.
  • Back in the Dialogflow console, select Integrations from the left-hand menu.
  • Find the Google Assistant card, and select Integration settings.
  • If you encounter a Check auto-preview setting dialog, leave Auto-preview changes enabled.
  • Select Test. Dialogflow will now upload your agent and launch the Actions Simulator in a new tab. In the Suggested input field, type “Talk to my test app” and press the Enter key on your keyboard.
  • Type your name, and press Enter. Dialogflow should now address you by name!

Keep the conversation going with follow-up intents

Since we asked a question, we need to be able to handle the answer! Let’s create two follow-up intents to handle a “Yes” and “No” response:

  • Select Intents from the left-hand menu.
  • Hover over the create_name text, and select Add follow-up intent when it appears.
  • Select Yes from the dropdown menu.
  • Repeat the above steps, but this time select No.

You can now edit these intents. Let’s start with “no”:

  • Select the create_name – no intent.
  • Click to expand the Responses section.
  • Enter the following static response: “Okay, see you next time!”
  • Since we’ve said our goodbyes, find the Set this intent as end of conversation slider, and drag it to the On position.
  • Scroll to the top of the screen, and then click Save.

Now we need to edit the “yes” intent:

  • Select Intents from the left-hand menu.
  • Select the create_name – yes intent.
  • Expand the Responses section.
  • Enter the following response: “Would you like to hear a bad joke about cats or dogs?”
  • Click Save.

Creating a custom entity

So far, we’ve stuck with Dialogflow’s ready-made system entities, such as @sys.given-name, but you can also create your own entities. Since there currently isn’t a or entity, we’ll need to define them as custom entities:

  • Select Entities from the left-hand menu.
  • Click the Create entity button.
  • Name this entity catOrDog.
  • Select Click here to add entity.
  • Under Enter reference value, type “Cat.”
  • Similar to training phrases, you need to enter a few synonyms representing the different ways that users may indicate they want to hear a joke about cats. After typing each synonym, press Enter.
  • Select the subsequent Click here to edit entry field.
  • Enter “Dog” as the reference value, and then add some synonyms.
  • Click Save.

Using your custom entities

You apply these custom entities to your intents, in exactly the same way as system-defined entities:

  • In the left-hand menu, select Intents.
  • Click Create intent.
  • Name this intent “Dog or cat joke.”
  • Under Training phrases, enter “Dog” and “Cat.” Dialogflow should recognize these values, and map them to your catOrDog entity.

Unleash your best bad jokes!

Our final task is to start inflicting bad jokes on the user:

  • Select Intents from the left-hand menu.
  • Click to expand the create_name intent.
  • Hover over the create_name – yes follow-up intent, and then select Add follow-up intent.
  • Select Custom from the dropdown.
  • Select your intent, which launches the intent editor.
  • The automatically-generated intent name is pretty long, so let’s change it to “Dog.”
  • Under parameter name, type “Dog.”
  • In Entity, start typing “catOrDog,” and then select it from the dropdown when it appears.
  • Under Value, type “Dog.”
  • Enter training phrases like “I want to hear a dog joke,” “tell me a bad joke about dogs,” or “dogs.”
  • In the Text response section, type your most cringeworthy canine joke. I’m using “What do you call a large dog that meditates? Aware wolf.”
  • Nobody will want to continue talking to our Action after such a terrible joke, so enable the Set this intent as end of conversation slider.
  • Click Save.

Repeat the above steps, to create your cat intent, and that’s all there is to it!

The only thing left to do is fire up the Actions Simulator and see how the Action handles the various responses.

Wrapping up

This Action may be straightforward, but it demonstrates many of the tasks you’ll perform over and over when creating your own Actions. You can take these techniques for learning the user’s name, extracting parameters, delivering static and dynamic responses, and training your Dialogflow agents, and apply them to pretty much any Action project.

If you decide to develop Google Assistant Actions that do more than deliver a couple of bad jokes, share your work with others and submit your Action for approval!

Will you develop for the Actions directory? Let us know in the comments below!

Android DevelopmentApp development, Google Assistant, Google Home

  1. Pretty and posh vanity
  2. Minecraft tnt videos
  3. Vicious weapon pathfinder
  4. Boxy jacket sewing pattern

Set up Google Assistant with your Xbox console

The Xbox Action for Google Assistant lets you control your Xbox Series X|S or Xbox One console from any Google Assistant or Google Home-enabled device.

  1. Set your power mode to instant-on:
    1. Press the Xbox button  to open the guide.
    2. Select Profile & system > Settings > General > Power mode & startup.
    3. Select Instant-on from the Power mode dropdown menu.
  2. Enable digital assistants. Go to Profile & system > Settings > Devices & connections > Digital assistants, and then select Enable digital assistants.
  3. Sign in to your Xbox.
  1. In the Google Home app for iOS or Android:
    1. Tap + Add.
    2. Tap Set up device.
    3. Tap Have something already set up?
    4. Search for Xbox.
  2. Select Xbox and sign in with the Microsoft account you use on Xbox.
  3. Follow the instructions to pair your Xbox with your Google Assistant device and provide your Xbox device name.

Google Assistant commands for Xbox

When controlling your Xbox with Google Assistant, use the device name you added during setup. If you named your console ‘Xbox’, just use the commands below. If not, substitute the device name you provided during setup.

Here are some commands to try:

  • “Hey Google, play Fortnite on Xbox”
  • “Hey Google, turn off Xbox”
  • “Hey Google, turn on Xbox”
  • “Hey Google, pause Xbox”
  • “Hey Google, resume on Xbox”
  • “Hey Google, volume up on Xbox”
  • “Hey Google, volume down 5 on Xbox”
  • “Hey Google, launch YouTube on Xbox”
  • “Hey Google, mute Xbox”
  • “Hey Google, record that on Xbox”
  • “Hey Google, take a screenshot on Xbox”

Did this resolve the issue?

Still need help?

Request a call, chat online, and more.

Contact times

Phone support

Monday to Friday: 6:00am-5:00pm PTSaturday to Sunday: 6:00am-5:00pm PT

Web chat

Monday to Sunday: 24 hours a day


Actions on Google: Actions SDK Conversation Components Sample

This code sample was built using the legacy Actions SDK. We now recommend using Actions Builder or the new Actions SDK to develop, test, and deploy Conversational Actions.

This sample demonstrates Actions on Google features including rich responses -- using the Node.js client library and deployed on Cloud Functions for Firebase.

Setup Instructions


  1. Node.js and NPM
    • We recommend installing using NVM
  2. Install the Firebase Functions CLI
    • We recommend using version 6.5.0,
    • Run with your Google account
  3. Install the gactions CLI
    • You may need to grant execute permission, ‘chmod +x ./gactions’


Actions Console

  1. From the Actions on Google Console, New project (this will become your Project ID) > Create project > under More options select Actions SDK > keep the Use Actions SDK to add Actions window open, will revisit in a later step.

Firebase Deployment

  1. On your local machine, in the directory, run
  2. Run to deploy the function
  3. Update the action package, , replacing the placeholder value with the value for Function URL obtained from the previous step.
  4. From the top level directory in this sample, run with your Project ID.
  5. Back in the Actions console, from the pop up window > select OK.
  6. From the top menu click Test to open the Actions on Google simulator then say or type .

Running this Sample

  • You can test your Action on any Google Assistant-enabled device on which the Assistant is signed into the same account used to create this project. Just say or type, “OK Google, talk to my test app”.
  • You can also use the Actions on Google Console simulator to test most features and preview on-device behavior.

References & Issues

Make Contributions

Please read and follow the steps in the




Your use of this sample is subject to, and by using or downloading the sample files you agree to comply with, the Google APIs Terms of Service.


Console actions on google

How to configure the 'Actions on Google' console for Google Assistant

Engineering GoogleAssistant

Time Required : less than 10 minutes. Technologies : None. Prerequisites : None. This tutorial will go over how to configure the ‘Actions on Google’ console so…

Free, Secure and Trusted Way to Authenticate Your Visitors

Add login to your website in 5 minutes completely for free!

Free Sign UpNo hidden costs. No credit card needed.

Time Required : less than 10 minutes.

Technologies : None.

Prerequisites : None.

This tutorial will go over how to configure the ‘Actions on Google’ console so that it can be used for your Google Assistant actions/events that can be accessed anywhere the Google Assistant is available from phones to Google Home products.


  1. Create an Actions project and a Dialogflow agent here.

    1. Add/import project. Screen Shot 2018 05 30 at 9 47 33 AM 300x280
    2. Click on Skip(in the upper right corner) choosing a category and click Build -> Actions in the left nav to add your first actions.
      Screen Shot 2018 05 30 at 10 02 46 AM 300x177
  2. Configuration for your action intent in the dialogflow console.

    1. In the Intent section, enter your training phrases. Start with “talk to”, “speak to”, “ask” and etc, learn more here.Screen Shot 2018 05 30 at 10 41 30 AM 300x288
    2. Enter the default text response. This will be the default response for your action until you link your account with LoginRadius and build your customized response. (This will return errors if you leave this empty, even if you handle the response in your code.)Screen Shot 2018 05 30 at 10 42 03 AM 300x193

By then, you should have finished the setup for google assistant.

Do you want a free authentication solution?

Add the world's most secure, reliable and easy to implement user authentication solution on your applications at $0Get Started Free

How to create a Google Action from Scratch - Actions on Google

"daughter, you probably don't remember, because you were still little. I didnt do it, because it seemed to me that you poop normally, but, as the recent incident with your tummy showed, its not. Quite so in reality. Mom refilled the mug with water, added a drop of shampoo, then went to the kitchen, took a teaspoon of. Salt from there, poured salt into the mug and stirred the liquid with a spoon.

You will also like:

Girl, what are your cool legs, such legs cannot be hidden under long clothes, said one boy. - And what funny panties, white as pure snow, added the second. - Beauty, and you would not want to take them off, and show us all your true beauty, suggested the third.

- Of course, I would like to, but not for you, she smiled coquettishly, knowing that Roman would not hear anything anyway.

1178 1179 1180 1181 1182