This page provides a reference for all system entities provided by Dialogflow.
If a system entity is not supported for your region and language, you have three options:
- If the system entity is extendable, you can use it in your agent by extending it with desired entity entries.
- You can use custom entities.
- You can use
@sys.any. For example, where you would normally use
@sys.person, create a form parameter,
@sys.anyentity type. The agent can prompt for the partial or full name when form filling.
There are many important best practices for using system entities described in the agent design best practices guide.
The table below describes all system entities. You can filter the table by system entity category, system entity name and/or extendibility.
Support for each system entity varies by the combination of region and language. The Availability column describes whether a system entity is supported in certain combinations of region and language. The following groups of regions are referenced in this column, where SER is an abbreviation for system entity regions:
|SER-All||All regions supported by Dialogflow|
The cells of this column list one or more region groups followed by a list of supported languages for each group. Some regions provide system entity support for each language that has an example in the example table below (you can filter this table by language), while others only support specific languages.
The table below provides input and output examples for all system entities. You can filter the table by language and/or system entity name. If an entity has no examples for a specific language, the entity does not support that language. See the limitations section for details.
The table below provides the units used by system entities. You can filter the table by language and/or measured quantity.