The Psychic in this sample can guess interesting secrets about you, like your name and where you are. This sample introduces permissions requests for user information on the Actions on Google platform.

1. Use the Actions on Google Console to add a new project with a name of your choosing and click Create Project.
2. Scroll down to the More Options section, and click on the Conversational card.
3. On the left navigation menu under BUILD, click on Actions. Click on Add Your First Action and choose your app's language(s).
4. Select Custom intent, click BUILD. This will open a Dialogflow console. Click CREATE.
5. Click on the gear icon to see the project settings.
6. Select Export and Import.
7. Select Restore from zip. Follow the directions to restore from the NamePsychic.zip file in this repo.
8. Deploy the fulfillment webhook provided in the functions folder using Google Cloud Functions for Firebase:
   1. Follow the instructions to set up and initialize Firebase SDK for Cloud Functions. Make sure to select the project that you have previously generated in the Actions on Google Console and to reply "N" when asked to overwrite existing files by the Firebase CLI.
   2. Obtain an API Key for the Google Maps Geocoding API following Step 1 of the instructions from this page.
   3. Run the following command replacing <THE_API_KEY> with your API Key for the Google Maps API: firebase functions:config:set maps.key="<THE API KEY>"
   4. In the Google Cloud Console API Library, enable the Static Maps API for your project.
   5. Run firebase deploy --only functions and take note of the endpoint where the fulfillment webhook has been published. It should look like Function URL (namePsychic): https://us-central1-YOUR_PROJECT.cloudfunctions.net/namePsychic
9. Go back to the Dialogflow console and select Fulfillment from the left navigation menu. Enable Webhook, set the value of URL to the Function URL from the previous step, then click Save.
10. Select Intents from the left navigation menu. Select the handle_permission fallback intent, scroll down to the Actions on Google section, check End Conversation, then click Save.
11. Select Integrations from the left navigation menu and open the Settings menu for Actions on Google.
12. Enter the following intents as Additional triggering intents
    • request_name_permission
    • request_location_permission
13. Enable Auto-preview changes and Click Test. This will open the Actions on Google simulator.
14. Type Talk to my test app in the simulator, or say OK Google, talk to my test app to any Actions on Google enabled device signed into your developer account.

For more detailed information on deployment, see the documentation.

• Actions on Google documentation: https://developers.google.com/actions/.
• If you find any issues, please open a bug here on GitHub.
• Questions are answered on StackOverflow.

Please read and follow the steps in the CONTRIBUTING.md.

See LICENSE.

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.

Actions on Google Developers Community on Google+ https://g.co/actionsdev.