Conversational Agents (Dialogflow CX): New Responsible AI fields are now available for the v3 and v3beta1 API endpoints. Responsible AI allows you to flag, filter or block harmful content.
Conversational Agents (Dialogflow CX): Dialogflow CX Messenger integration contained a vulnerability that allowed for authentication bypass when an agent was configured to use an authenticated API with a 3rd party identity. All versions released after August 20th, 2025 have been updated to protect from this vulnerability. No user action is required.
Conversational Agents (Dialogflow CX): Conversational Agents now supports log splitting for large Cloud Logging log entries.
]]>Conversational Agents (Dialogflow CX): Regular expression validation (Regex) is now available in Agent Settings and Entity Types.
]]>Conversational Agents (Dialogflow CX):You can now specify custom voice in the Conversation profiles menu in the console.
]]>Conversational Agents (Dialogflow CX): You can now configure service account authorization for both tools and webhooks. See the reference documentation for details.
Conversational Agents (Dialogflow CX): New fields temperature, input_token_limit and output_token_limit are now available for LlmModelSettings in the v3beta1 API. This allows you to adjust the model per playbook.
Conversational Agents (Dialogflow CX):The Block none safety feature in agent settings is no longer restricted access.
Conversational Agents (Dialogflow CX): The Entity Types console menu now allows you to set a page size for entity entries and excluded phrases. Pagination options are automatically displayed if there are more than 10 items listed.
]]>Dialogflow CX (Conversational Agents): The default models for data stores and playbooks have been upgraded as follows:
Data stores
gemini-2.0-flash-lite-001 to gemini-2.5-flash-lite.gemini-2.0-flash-001 to gemini-2.5-flash.gemini-2.0-flash-lite-001 to gemini-2.5-flash-lite.Playbooks:
gemini-2.5-flash.Dialogflow CX (Conversational Agents): The Dialogflow CX console will be deprecated on October 31, 2025. After that date all users will be automatically routed to the Conversational Agents console.
]]>Dialogflow CX (Conversational Agents): This is a correction of the release note posted on August 7, 2025. All deactivated models are now automatically upgraded to model gemini- 2.5-flash with the exception of generative fallback, which is automatically upgraded to gemini-2.5-flash-lite.
Dialogflow CX (Conversational Agents): The following regions are now available:
asia-southeast2europe-west4europe-west6Dialogflow CX (Conversational Agents) The model gemini-2.5-flash-lite is now available in all regions, and gemini-2.5-flash is now GA. These changes apply to the following features:
Dialogflow CX (Conversational Agents): New prompt security controls are available in agent settings. See the agent settings documentation for details.
]]>Dialogflow CX and Vertex AI: The gemini-1.0-pro, gemini-1.5-pro and gemini-1.5-flash models will be deprecated on September 1, 2025 and automatically upgraded to the gemini-2.0-flash-001 model. This change applies to Vertex AI agents and the following Conversational Agents generative features:
After the upgrade on September 1, 2025, gemini-2.0-flash-001 will be automatically selected in the console. We recommend that you upgrade to the new model early to allow enough time for testing and to ensure that your solution works as intended.
Conversational Agents: Routine playbooks are now generally available.
Conversational Agents: Parameter passing is now available and documented between routine playbooks, task playbooks, and flows.
]]>Conversational Agents: 21 new Chirp 3 HD voices are now available across 34 locales.
Conversational Agents data stores: Conversational Agents now supports AlloyDB AI, Bigtable, Firestore, Spanner and Cloud SQL data store source as public GA features; Microsoft Entra ID source has now private GA support. See the data store documentation for a complete list.
]]>Conversational Agents: CMEK is now available in EU regions.
Conversational Agents: The conversational history flow analysis feature is now available.
Conversational Agents: The model gemini-2.5-flash is now available in all regions. This change applies to the following features:
Conversational Agents data stores: You can now create some data store types directly within the Conversational Agents console rather than needing to use AI Applications. See the data store creation documentation for details.
Conversational Agents data stores: Conversational Agents now supports AlloyDB, Bigtable, Firestore, Spanner and Cloud SQL data store sources as public GA features. Microsoft Entra ID source has now private GA support.
]]>Conversational Agents: New Chirp 3 HD Cloud Text-to-Speech voice Autonoe is now available.
Conversational Agents: Conversational Agents console now supports test cases.
Data store handlers: Data store handler use tracking for billing purposes has been corrected.
Conversational Agents: Service agent access tokens used for authentication by both webhooks and tools are now discontinued as mentioned in notification emails to customers earlier this year. Most customers can use service accounts instead.
]]>Dialogflow CX (Conversational Agents): Models gemini-2.0-flash-001 and gemini-2.0-flash-lite-001 are now GA. They are available in all supported regions.
This change applies to the following features:
Dialogflow CX (Conversational Agents): You can now create personalized voice models with voice cloning.
Dialogflow CX (Conversational Agents): You can now use the console to test your tools.
Dialogflow CX (Conversational Agents): You can now use code blocks to get better control over playbooks.
]]>Dialogflow CX (Conversational Agents): Data store tools no longer require the use of a playbook and can be used with any agent. For information about configuring data store tools for a flow-based agent, see the data store tools documentation.
Dialogflow CX (Conversational Agents): The gemini-1.0-pro model is deprecated as of March 24, 2025 and has been automatically upgraded to the gemini-1.5-flash-001 model. This change applies to the following features:
Dialogflow CX (Conversational Agents): AI generation of language-specific information, entities and training phrases is now GA.
Dialogflow CX (Conversational Agents): All prebuilt agents are now GA.
]]>Dialogflow CX (Conversational Agents) data stores: Dialogflow now supports additional native and third-party data store sources as a private GA feature. For a list of data store sources, integration instructions, and the request form to be added to the allowlist, see the data stores documentation.
Dialogflow CX (Conversational Agents) data store handlers: The method of adding data store handlers to an agent has been streamlined. You are no longer required to create a Chat app on Agent Builder. For updated implementation instructions, see the data stores tools documentation.
]]>The Conversational Agents console is now generally available (GA). This console combines the power of Generative AI playbooks and data stores with deterministic flows. Additional features:
https://conversational-agents.cloud.google.com/.Conversational Agents: Conversational Agents now supports multiple tool versions in addition to playbooks and flows. See the versions and environments documentation for details.
Conversational Agents playbooks: Playbooks now support 38 languages. Playbook language support is displayed on the language support page. Supported languages have been tested for quality with the gemini-2.0-flash-001 and gemini-1.5-flash-002 models.
Conversational Agents: New Chirp 3 HD Cloud Text-to-Speech voices are now available.
Conversational Agents playbooks: New model gemini-2.0-flash (Preview) is now available. For more information and supported regions, see Model support.
Conversational Agents: You can now toggle a Show latency option in the Conversational Agents Console simulator to view latency per conversation turn for simulator conversations. To view latency breakdown, click the total latency value for the conversation turn. Latency values are also shown in the original response, Cloud logging, and BigQuery export.
Be aware that latency values are not recorded directly in the logs, but are represented as startTime and completeTime values in the traceBlocks field.
Conversational Agents playbooks: You can now enable DTMF in playbook Settings and as a conditional actions as a Preview feature. See the playbook settings and DTMF for telephony integrations pages for more information.
]]>Dialogflow CX (Conversational Agents): Customer-managed encryption keys (CMEK) is now a GA feature.
]]>Dialogflow CX (Conversational Agents) data store handlers: Model gemini-2.0-flash-lite-001 is now a Preview feature available in the following regions: global, us, us-central1, us-east1, us-west1, europe-west1, europe-west4.
Dialogflow CX (Conversational Agents) generators: Model gemini-2.0-flash-001 is now a GA feature available in the following regions: global, us, us-central1, us-east1, us-west1, europe-west1, europe-west4.
Dialogflow CX (Conversational Agents): The Conversational Agents console has moved to a new location.
Dialogflow CX (Conversational Agents): You can now use the console search feature to search for all resources, including playbooks, examples, and tools.
Dialogflow CX (Conversational Agents): Playbooks now support the following new features:
Dialogflow CX (Conversational Agents): You can now use the Conversational Agents console to manage languages.
Dialogflow CX (Conversational Agents) data store handlers: New model gemini-2.0-flash-001 is now available to data store handlers as a Preview feature. This launch is limited to the following regions: global, us, us-central1, us-east1, us-west1, europe-west1, europe-west4.
Dialogflow CX (Conversational Agents): Text-to-speech used by Dialogflow now supports new Chirp 3 HD voices.
Dialogflow CX (Conversational Agents): Git export/restore now supports additional Git providers and Google Secrets for token storage.
]]>Dialogflow CX (Conversational Agents): Text-to-speech used by Dialogflow now supports new Chirp HD voices.
Dialogflow CX (Conversational Agents) & ES: Text-to-speech removed support for voices across European markets. Affected users were sent an email announcement.
]]>Conversational Agents (CX), ES & Agent Assist: Starting February 24, 2025, a limit of 5 phone numbers per project will be enforced. This limit doesn't apply to the global region. For instructions on deleting unused phone numbers and resolving the limit issue, see the RESOURCE_EXHAUSTED troubleshooting section. If you have a business requirement to increase the limit, request to increase the Phone numbers quota specifying the region and providing detailed justification for your request.
The Conversational Agents console has launched for preview to create agents that can use a combination of generative and deterministic features. See how we intend on migrating to this new console.
]]>Dialogflow CX (Conversational Agents): Dialogflow CX has launched a new feature that allows you to auto-generate and auto-translate Intent training phrases, Entity synonyms, and Fulfillment phrases in the language of your choice. See the documentation for details.
Dialogflow CX (Conversational Agents): You can now require a full match for banned phrases in addition to a partial match. If enabled, a full match requires the input to be matched exactly in order to trigger a ban. For more information about setting banned phrases, see the documentation.
Dialogflow CX (Conversational Agents): Service directory support is now enabled for flexible webhooks. See the webhooks documentation for details.
]]>Dialogflow CX (Conversational Agents): You can now set either a partial match or a full match to banned phrases. This setting applies to playbooks, datastores, and generators. You can enable and test this feature in Agent Settings > Generative AI > Banned phrases > Match requirements.
]]>Dialogflow CX data stores: The following languages are now GA. See the language support page for details.
Dialogflow CX: You can now configure an access token name in Dialogflow Messenger to store the end user's authentication when they sign in, and then use it as the bearer token for tool authentication. See the Dialogflow Messenger documentation for more information about enabling this feature.
]]>Dialogflow CX: New feature Context token limits has been added to Agent Settings > Generative AI. You can use this feature to set a percentage of the token budget to be reserved for conversation history, as a maximum. See the Agent Settings documentation for details.
Data store tools: You can now optimize the RAG performance of data store tools used by Playbooks. See the documentation for details.
Generators and data store handlers: The model gemini-1.5-flash-002 is now GA.
Data store handlers: The default generative model has been changed to gemini-1.5-flash-001.
Dialogflow CX: As of August 2024, us-dialogflow.* has been re-introduced as the canonical endpoint for the US multi-region. The usa-dialogflow.* endpoint is still supported as an alias. See the regionalization documentation for details.
Dialogflow CX & ES: In order to increase the stability of Cloud Text-to-speech, out-of-quota requests for Journey Voices will now be fulfilled with a fallback voice of the same speaker persona. To opt out, contact your Google account team.
Dialogflow CX & ES: Dialogflow now supports A-law encoding in addition to Mu-law encoding for input and output audio. A-law and Mu-law are the two available formats in G.711.
]]>