Each intent parameter has a type, called the entity type, which dictates exactly how data from an end-user expression is extracted.
Dialogflow provides predefined system entities that can match many common types of data. For example, there are system entities for matching dates, times, colors, email addresses, and so on. You can also create your own custom entities for matching custom data. For example, you could define a vegetable entity that can match the types of vegetables available for purchase with a grocery store agent.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-27 UTC."],[[["\u003cp\u003eEntityType dictates how data is extracted from end-user expressions, defining the type of data expected for each intent parameter.\u003c/p\u003e\n"],["\u003cp\u003eDialogflow offers predefined system entities for common data types like dates and email addresses, and allows custom entities for specific data, such as a vegetable entity for a grocery store agent.\u003c/p\u003e\n"],["\u003cp\u003eThe JSON representation for an EntityType includes fields like \u003ccode\u003ename\u003c/code\u003e, \u003ccode\u003edisplayName\u003c/code\u003e, \u003ccode\u003ekind\u003c/code\u003e, \u003ccode\u003eautoExpansionMode\u003c/code\u003e, \u003ccode\u003eentities\u003c/code\u003e, and \u003ccode\u003eenableFuzzyExtraction\u003c/code\u003e, which defines its structure and properties.\u003c/p\u003e\n"],["\u003cp\u003eThe methods associated with EntityTypes enable actions such as batch deletion, batch updating, creation, deletion, retrieval, listing, and patching of entity types.\u003c/p\u003e\n"]]],[],null,["# REST Resource: projects.locations.agent.entityTypes\n\n- [Resource: EntityType](#EntityType)\n - [JSON representation](#EntityType.SCHEMA_REPRESENTATION)\n- [Methods](#METHODS_SUMMARY)\n\nResource: EntityType\n--------------------\n\nEach intent parameter has a type, called the entity type, which dictates exactly how data from an end-user expression is extracted.\n\nDialogflow provides predefined system entities that can match many common types of data. For example, there are system entities for matching dates, times, colors, email addresses, and so on. You can also create your own custom entities for matching custom data. For example, you could define a vegetable entity that can match the types of vegetables available for purchase with a grocery store agent.\n\nFor more information, see the [Entity guide](https://cloud.google.com/dialogflow/docs/entities-overview)."]]