Dialogflow ES Glossary



Dialogflow actions are primarily used to tell your webhook code that a specific intent has fired. Now, you can accomplish the same thing by just using the name of the intent. (In fact, that’s what most of the code samples provided by the Dialogflow team do).

However, using the action has a specific benefit – you can update the name of an intent (maybe you are correcting a typo) without having to go and modify your webhook code.

Actions SDK

The Actions SDK is a Software Development Kit (SDK) which is used to develop apps for the Google Assistant. In particular, it provides an interface whereby you can perform specific actions on your Google Assistant device. When combined with an NLU engine (bot framework) such as Dialogflow, it will be possible to build powerful voice and natural language based apps.

Click here to read about the difference between the Actions SDK and Dialogflow.


Client Access Token

The client access token provided a way to integrate with the first version of the Dialogflow API (v1).

Since Dialogflow API moved to version v2, the client access token has been deprecated and cannot be used for Dialogflow integrations anymore.

This website contains affiliate links. See the disclosure page for more details. 
"The magic key I needed as a non-programmer"

The custom payload generator was the magic key I needed (as a non-programmer) to build a good demo with rich responses in DialogFlow Messenger. I've only used it for 30 minutes and am thrilled. I've spent hours trying to figure out some of the intricacies of DialogFlow on my own. Over and over, I kept coming back to Aravind's tutorials available on-line. I trust the other functionalities I learn to use in the app will save me additional time and heartburn.

- Kathleen R
Cofounder, gathrHealth
In this free course, I provide some tips for managing large Dialogflow ES bots without compromising on accuracy.