Stay organized with collections
Save and categorize content based on your preferences.
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.
Entity terminology
The term entity is used in this documentation and in the Dialogflow Console
to describe the general concept of entities.
When discussing entity details,
it's important to understand more specific terms:
Entity type:
Defines the type of information you want to extract from user input.
For example, vegetable could be the name of an entity type.
Clicking Create Entity from the Dialogflow Console creates an entity type.
When using the API,
the term entity type refers to the
EntityType
type.
Entity entry:
For each entity type, there are many entity entries.
Each entity entry provides a set of words or phrases that are considered equivalent.
For example, if vegetable is an entity type, you could define these three entity entries:
carrot
scallion, green onion
bell pepper, sweet pepper
When editing an entity type from the Dialogflow Console,
each row of the display is an entity entry.
When using the API,
the term entity entry refers to the
Entity type (EntityType.Entity or EntityType_Entity
for some client library languages).
Entity reference value and synonyms:
Some entity entries have multiple words or phrases
that are considered equivalent,
like the scallion example above.
For these entity entries, you provide one reference value
and one or more synonyms.
[[["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-08-07 UTC."],[[["\u003cp\u003eEntity types define the kind of information extracted from user input, such as "vegetable".\u003c/p\u003e\n"],["\u003cp\u003eDialogflow offers predefined system entities for common data types and allows the creation of custom entities.\u003c/p\u003e\n"],["\u003cp\u003eEntity entries provide equivalent words or phrases for a given entity type, such as "carrot" or "scallion" for the vegetable entity type.\u003c/p\u003e\n"],["\u003cp\u003eEntity entries can include a reference value and synonyms, where multiple words or phrases are considered equivalent.\u003c/p\u003e\n"],["\u003cp\u003eThe term "entity" broadly describes the concept of entities, with more specific terms like "entity type" and "entity entry" used for detailed discussions.\u003c/p\u003e\n"]]],[],null,["# Entities\n\nEach intent\n[parameter](/dialogflow/docs/intents-actions-parameters#params)\nhas a type, called the\n\n*entity type*,\n\nwhich dictates exactly how data from an end-user expression is extracted.\n\n\nDialogflow provides predefined\n[system entities](/dialogflow/docs/entities-system)\nthat can match many common types of data.\nFor example, there are system entities for matching dates, times, colors, email addresses, and so on.\nYou can also create your own\n[custom entities](/dialogflow/docs/entities-custom)\nfor matching custom data.\nFor example, you could define a *vegetable* entity\nthat can match the types of vegetables available for purchase with a grocery store agent.\n\nEntity terminology\n------------------\n\nThe term *entity* is used in this documentation and in the Dialogflow Console\nto describe the general concept of entities.\nWhen discussing entity details,\nit's important to understand more specific terms:\n\n- **Entity type** :\n Defines the type of information you want to extract from user input.\n For example, *vegetable* could be the name of an entity type.\n Clicking **Create Entity** from the Dialogflow Console creates an *entity type* .\n When using the API,\n the term *entity type* refers to the\n [`EntityType`](/dialogflow/docs/reference/common-types#entitytypes)\n type.\n\n- **Entity entry** :\n For each entity type, there are many *entity entries* .\n Each entity entry provides a set of words or phrases that are considered equivalent.\n For example, if *vegetable* is an entity type, you could define these three entity entries:\n\n - carrot\n - scallion, green onion\n - bell pepper, sweet pepper\n\n When editing an entity type from the Dialogflow Console,\n each row of the display is an *entity entry* .\n When using the API,\n the term *entity entry* refers to the\n `Entity` type (`EntityType.Entity` or `EntityType_Entity`\n for some client library languages).\n- **Entity reference value and synonyms** :\n Some entity entries have multiple words or phrases\n that are considered equivalent,\n like the *scallion* example above.\n For these entity entries, you provide one *reference value*\n and one or more *synonyms*."]]