This document contains the current quotas and limits for use of Dialogflow. We reserve the right to change these constraints, and this page will be updated to reflect any changes.
Definitions
The following terms are used to describe pricing and quotas:
- Request: A request is defined as any call to the Dialogflow service, whether direct with API usage or indirect with integration or console usage. Depending on the task and design of the agent, the number of requests needed for an end-user to accomplish a task with a Dialogflow agent can vary greatly.
-
Session:
A session is a conversation between an end-user and a Dialogflow agent.
A session remains active and its data is stored for 30 minutes
after the last request is sent for the session.
A session can be either a chat session or a voice session.
For the purpose of calculating prices and quotas,
one conversation can count as multiple sessions:
- Chat session: A chat session only uses text for requests and responses. If a chat session has more than 40 requests, it is counted as multiple sessions with at most 40 requests per session. For example, if a session has 81 queries, it will be counted as 3 sessions.
- Voice session: A voice session uses audio for requests, responses, or both. If a voice session has more than 10 minutes of audio, it is counted as multiple sessions with at most 10 minutes per session. For example, if a session has 21 minutes of audio, it will be counted as 3 sessions.
- Consumer projects and resource projects: If you use multiple projects, it is possible that the project associated with your request authentication (consumer project) is not the same project that is associated with the agent in the request (resource project). In this case, the consumer project is used to determine prices and quotas. For more information, see Using multiple projects.
Quotas
Quotas are default constraints applied to your project. If you are using a paid edition, you can request a quota increase. The purpose of quotas is to throttle service load per client, which protects a service from being overloaded and a client from unexpected resource usage.
Dialogflow quotas vary, depending on the edition of your agent. Quotas apply to each project and are shared across all applications and IP addresses using a project.
The quotas listed below are the commonly encountered quotas. To review all quotas, see the GCP Console Dialogflow quotas page. To request a higher quota, click Apply for a higher quota in the quota edit form to submit a Dialogflow Quota Increase Request.
Quotas table
The following tables provide a quota comparison for editions by agent type. Unless a feature is indicated as included, pricing and quotas are cumulative for all features used by a request.
CX Agent
Feature | CX Edition |
---|---|
Text |
|
Audio input/output (speech recognition, speech-to-text, STT, speech synthesis, text-to-speech, TTS) |
|
Design-time requests For example, calls to build or update an agent. |
|
Other session requests For example, setting session entities or updating/querying context. |
|
ES Agent
Feature | Trial Edition | Essentials Edition |
---|---|---|
Text ¶ |
|
|
Audio input † (also known as speech recognition, speech-to-text, STT) |
|
|
Audio output † (also known as speech synthesis, text-to-speech, TTS) |
|
|
Knowledge Connectors (Beta) |
|
|
Sentiment analysis |
|
|
Dialogflow phone gateway (Beta) Includes audio input and output. |
|
|
Mega agent |
|
|
Design-time requests For example, calls to build or update an agent. |
|
|
Other session requests For example, setting session entities or updating/querying context. |
|
|
† |
Each
StreamingDetectIntent
stream is considered a single request,
even though the stream might include multiple frames of
StreamingDetectIntentRequest audio within the stream.
|
‡ | "Phone minutes per minute" is the total sum of time per minute that is used by all users making calls through the phone system. For example: in one 60-second time period one user is on for 60 seconds, a second for 30 seconds, and a third for 30 seconds. This is calculated as 2 minutes per minute. More minutes per minute allows more users to use the system simultaneously. |
# | Features marked as unlimited are still potentially limited by use of other features. For example, if your edition provides unlimited quota for knowledge connectors, a text request that uses knowledge connectors is still limited by the quota for text requests. |
¶ | Google Assistant audio input and output is considered a text request. |
Limits
Limits are fixed constraints, which cannot be increased. Many resources and fields have count, duration, or length limitations, which are fixed constraints for the service implementation.
The following tables list commonly encountered limits. Feature-specific documentation and API reference documentation may provide additional limits.
Count limits
CX Agent
Description | Limit |
---|---|
Maximum number of agents per Google Cloud project | 100 |
Maximum number of flows per agent | 20 |
Maximum number of entity types per agent | 250 |
Maximum number of webhooks per agent | 100 |
Maximum number of environments per agent | 20 |
Maximum number of pages per flow | 250 |
Maximum number of route groups per flow | 100 |
Maximum number of versions per flow | 20 |
Maximum number of referenced intents per flow | 2000 |
Maximum number of training phrases per intent and per language (except "Default Negative Intent") | 2000 |
Maximum number of parameters per intent | 20 |
Maximum number of entity entries per entity | 30,000 |
Maximum number of entity synonyms per entity entry | 200 |
Maximum number of entity reference values and synonyms per agent and per language | 1,000,000 |
Maximum number of parameters per page | 20 |
Maximum number of routes per page | 2000 |
Maximum number of event handlers per page | 100 |
Maximum number of routes per route group | 2000 |
ES Agent
Description | Limit |
---|---|
Maximum number of agents per region and per Google Cloud project | 1 |
Maximum number of intents | 2000 |
Maximum number of entity types | 250 |
Maximum number of training phrases per intent and per language * | 2000 |
Maximum number of training phrases per agent and per language * | 100,000 |
Maximum number of entity entries | 30000 |
Maximum number of entity synonyms per entity entry | 200 |
Maximum number of entity reference values and synonyms per agent and per language * | 1,000,000 |
Maximum number of parameters per intent | 20 |
Maximum number of input contexts per intent | 5 |
Maximum number of output contexts per intent | 30 |
Maximum number of text responses per intent and per language * | 30 |
Maximum number of prompts per parameter and per language † | 30 |
* | All limits related to intents that have a language component are validated on a per language basis. For example, if your agent supports English and French, an intent can have at most 2000 English training phrases and 2000 French training phrases. |
† | For example, if your agent supports English and French, a parameter can have at most 30 English prompts and 30 French prompts. |
Duration limits
CX Agent
Description | Limit |
---|---|
Maximum timeout per webhook | 30 seconds |
ES Agent
Description | Limit |
---|---|
Maximum telephony call duration | 3.5 hours |
Length limits
CX Agent
Description | Limit |
---|---|
Maximum training phrase length | 768 characters |
Maximum text response length | 4,000 characters |
Maximum detect intent text input length | 256 characters |
ES Agent
Description | Limit |
---|---|
Minimum agent name length | 1 character |
Maximum agent name length | 150 characters |
Maximum agent description length | 500 characters |
Maximum intent name length | 100 characters |
Maximum entity type name length | 30 characters |
Maximum training phrase length | 768 characters |
Maximum action name length | 250 characters |
Maximum context name length | 250 characters |
Maximum entry value length | 512 characters |
Maximum parameter name length | 30 characters |
Maximum text response length | 4000 characters |
Maximum detect intent text input length * | 256 characters |
Maximum event name length | 150 characters |
* | This limit is enforced by the Dialogflow service. If you are using an integration, the integration platform may have a smaller limit. See the details for your integration. |
Size limits
ES Agent
Description | Limit |
---|---|
Maximum agent size (unzipped content) for agent import/restore | 50 MB |