Dialogflow Secrets
Dialogflow V2 Secret For NLP Detection
- Login to your Dialogflow account
- Click on the settings gear wheel next to the agent you want to connect to

- Click on the Service Account link listed

- This will take you to the IAM & admin console in the Google Cloud Platform
- Create a Service Account or Generate a Key for an Existing Service Account

- You’ll need to Download the Key (this is a JSON file)

- Store your secrets
- In ServisBOT, click to “Secrets Management” and then “Create Secret”
- Select Dialogflow V2 in the Template drop down
- Upload the file you just downloaded from Dialogflow
- Save your Secrets
Dialogflow V2 Secret for Managing Intents with ServisBOT
To use SBIntents with a Dialogflow agent additional permissions are required in order to successfully train a bot.
-
Login to your Dialogflow account
-
Click on the settings gear wheel next to the agent you want to connect to

-
Click on the Service Account link listed
This will take you to the IAM & admin console in the Google Cloud Platform. Take note of an existing email
for a service account.
-
Click on IAM
in the left menu. If you have a service account there with the role Dialogflow API Admin
skip this step.
Otherwise, click select and edit an existing member.

-
Add a role for project
-> owner

-
Save the change and navigate back to Service Accounts
.
The member should now be listed on the IAM page with an Owner role.

-
You’ll need to Download the Key (this is a JSON file)

-
Store your secrets
- In the portal
Secrets
section, click to “Create Secret”
- Select Dialogflow V2 in the Template drop down
- Upload the file you just downloaded from Dialogflow
- Save your Secrets
Alternatively you can map the values of the fields in the Dialogflow JSON file directly.
- [user@mail.com] with the information in the client_email field from the json file
- [some-private-key] with the information in private_key field from the json file - all of it, even “—–BEGIN PRIVATE KEY”
- [someproject-id] with the information in the project_id field from the json file
Do not use the private-key-id in the private_key field this is a common mistake