Query a database

Your webhook currently uses hardcoded data in the accountBalanceCheck function. In this step of the tutorial, you will create a Spanner database, populate it with balance data, and update your function to query the database.

Project configuration

It is important that your Dialogflow agent and the database are both in the same project. This is the easiest way for your function to have secure access to your database. Also, you must enable the Spanner API.

Before creating the database, select your project from the Google Cloud console.

Go to project selector
Enable the Spanner API for the project.

Enable the Spanner API

Create a Spanner instance

When you first use Spanner, you must create an instance, which is an allocation of resources that are used by Spanner databases in that instance.

In the Google Cloud console, go to the Spanner Instances page.

Go to Spanner instances
Click Create instance.
For the instance name, enter Tutorial Instance.
The instance ID is automatically entered based on the instance name.
In Choose your configuration, retain the default option Regional and select the same region location that you chose when creating the function.
In Allocate compute capacity, enter 100 processing units. This provides a minimal capacity for the tutorial.
Click Create. The Google Cloud console displays the Overview page for the instance you created.

Create a Spanner database

Now that you have an instance, you need to create a database. To create a database:

In the instance Overview page, click Create database.
For the database name, enter tutorial-database.
Select the Google Standard SQL database dialect.
Click Create. The Google Cloud console displays the Overview page for the database you created.

Create tables for your database

Now that you have a database, you need to create tables for the database. To create tables:

In the Tables section of the database Overview page, click Create table.

In the Write DDL statements page, enter:

CREATE TABLE Checking (
  AccountId INT64,
  Balance INT64,
) PRIMARY KEY(AccountId);

Click Submit. The Google Cloud console returns to the database Overview page and shows that Schema updates are underway. Wait until the update is complete.
In the Tables section of the database Overview page, click Create table.

In the Write DDL statements page, enter:

CREATE TABLE Savings (
  AccountId INT64,
  Balance INT64,
) PRIMARY KEY(AccountId);

Click Submit. The Google Cloud console returns to the database Overview page and shows that Schema updates are underway. Wait until the update is complete.

Insert data into your tables

Now that your database has tables, you need to add data to the tables. To add data:

In the list of tables on the database Overview page, click the Checking table. The Google Cloud console displays the table's Schema page.
In the left navigation menu, click Data to display the table's Data page.
Click Insert. The Google Cloud console displays the table's Query page with a new query tab that contains INSERT and SELECT statements. Overwrite those statements with the following:
```
INSERT INTO Checking (AccountId, Balance)
VALUES(1, 1000),
      (2, 2000);
```
Click Run.
In the left navigation menu, click Data again to display the table's data. Confirm that the table contains the desired data.
Click the tutorial-database: Overview link to return to the database overview page.
In the list of tables on the database Overview page, click the Savings table. The Google Cloud console displays the table's Schema page.
In the left navigation menu, click Data to display the table's Data page.
Click Insert. The Google Cloud console displays the table's Query page with a new query tab that contains INSERT and SELECT statements. Overwrite those statements with the following:
```
INSERT INTO Savings (AccountId, Balance)
VALUES(1, 10000),
      (2, 20000);
```
Click Run.
In the left navigation menu, click Data again to display the table's data. Confirm that the table contains the desired data.

Update the Cloud Function to query the database

The accountBalanceCheck function in the webhook code checks whether specific environment variables are set with information for connecting to the database. If these environment variables are not set, the function uses a hardcoded account balance.

Now that you have a database set up, update your Cloud Function to set required environment variables:

Open the Cloud Functions overview page.

Go to Cloud Functions overview
Click the tutorial-banking-webhook function to go to its details page.
Click Edit.
Open the Runtime, build and connections settings section.
Select the Runtime tab.
Add the following variables in the Runtime environment variables section:
- PROJECT_ID: your project ID
- SPANNER_INSTANCE_ID: your Spanner instance ID (probably tutorial-instance)
- SPANNER_DATABASE_ID: your spanner database ID (probably tutorial-database)
Click Next.
Click Deploy.
Wait until the status indicator shows that the function has successfully deployed.

Test your agent

Your agent is now ready to try. Click the Test Agent button from the Dialogflow console to open the simulator. Attempt to have the following conversation with the agent:

Conversational turn	You	Agent
1	Hello	Hello, thanks for choosing ACME Bank.
2	I want to know my account balance	What account do you want the balance for: savings or checking?
3	Checking	Here's your latest balance: $10.00

If you examine the code, $10 is not the hardcoded value. This means that your webhook has successfully connected to the database, which does have a balance of $10.

Troubleshooting

The webhook code includes logging statements. If you are having issues, try viewing the logs for your Cloud Function.

If your function is not connecting to the database, and you see a permission error in the logs, you may need to fix the role for the default service account used by your function. This service account is of the form PROJECT_ID@appspot.gserviceaccount.com. You can fix this in one of the following ways:

If the default service account is shown on the IAM main page, change permissions for the service account. The Editor role will work, but you may want a more granular role in a production scenario.

Go to the IAM main page
If the a default service account is not shown on the IAM main page, grant the required role by adding the service account as a new principal.
Alternatively, you can use a service account that you create.

More information

For more information about the steps above, see:

Create a webhook service

Host your agent