Dialogflow Secrets

Dialogflow V2 Secret For NLP Detection

  1. Login to your Dialogflow account
  2. Click on the settings gear wheel next to the agent you want to connect to start
  3. Click on the Service Account link listed start
  4. This will take you to the IAM & admin console in the Google Cloud Platform
  5. Create a Service Account or Generate a Key for an Existing Service Account start
  6. You’ll need to Download the Key (this is a JSON file) start
  7. 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.

  1. Login to your Dialogflow account

  2. Click on the settings gear wheel next to the agent you want to connect to start

  3. Click on the Service Account link listed start This will take you to the IAM & admin console in the Google Cloud Platform. Take note of an existing email for a service account.

  4. Click on IAM in the left menu. If you have a service account there with the role Dialogflow API Admin skip this step. start Otherwise, click select and edit an existing member. start

  5. Add a role for project -> owner start

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

  7. You’ll need to Download the Key (this is a JSON file) start

  8. 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