September 01, 2020

Beta launch of Dialogflow CX. Dialogflow CX provides a new way of designing agents, taking a state machine approach to agent design. This gives you clear and explicit control over a conversation, a better end-user experience, and a better development workflow.

As part of introducing Dialogflow CX, some changes have been made to editions: Dialogflow Enterprise Edition is no longer used as an umbrella term for paid editions.

Dialogflow Standard Edition is now called Dialogflow Trial Edition.

Dialogflow Plus Edition and Dialogflow Essentials Edition have been merged to one Dialogflow Essentials (ES) Edition.

Dialogflow Customer Experience (CX) Edition is a new edition with a simpler pricing and quota model.

The service previously named Dialogflow is now called Dialogflow ES, and the term Dialogflow is now an umbrella term used to describe both the Dialogflow ES and Dialogflow CX services.

August 10, 2020

Beta launch of regionalization and data residency.

July 30, 2020

GA (general availability) launch of mega agents.

Beta launch of the Facebook Workplace integration.

July 27, 2020

Beta launch of Dialogflow Messenger. This new integration provides a customizable chat dialog for your agent that can be embedded in your website.

July 23, 2020

Amazon Alexa importer and exporter are no longer supported.

July 06, 2020

The Dialogflow Console has been upgraded with an improved Analytics page (Beta) that provides new metrics and data views.

June 29, 2020

The V1 API is in the process of a gradual shutdown. See the November 14, 2019 release note for details.

June 01, 2020

The shutdown of 7 integrations announced in January is now extended to July 6th, 2020.

May 29, 2020

The Dialogflow Facebook Messenger integration has been updated to to be compliant with newer Facebook Messenger API versions. If you have an agent that enabled this integration prior to today, you should have received an email from Dialogflow with upgrade instructions. If you have not received this email, please contact Dialogflow support.

May 17, 2020

Old Node.js client library require statements must be updated. Your require statements should look like this: const dialogflow = require('@google-cloud/dialogflow').v2; or this: const dialogflow = require('@google-cloud/dialogflow').v2beta1; Old syntax that does not include @google-cloud is now deprecated. The old syntax will continue to work, but you will not receive updates.

May 08, 2020

Beta launch of a one-click integration with the Voximplant telephony partner:

May 05, 2020

GA (general availability) launch of auto speech adaptation.

April 30, 2020

Beta launch of a one-click integration with a new telephony partner: Avaya

April 25, 2020

In May 2020, the Facebook Messenger integration will be updated, and you may notice slight changes related to fulfillment. To make sure that your Facebook Messenger bot keeps functioning normally, observe the following recommendations: To get the Facebook sender.id value, use the originalDetectIntentRequest.payload.data.sender field from the Dialogflow WebhookRequest message. To get the source field value, use the originalDetectIntentRequest.source field from the Dialogflow WebhookRequest message. To send rich response messages from your webhook to the Facebook Messenger integration, use the WebhookResponse.fulfillment_mesages[].payload field. In your webhook logic, don’t rely on the fields that are not documented in the official Facebook Messenger API. If you have any questions, reach out to your primary support channel.

April 20, 2020

Beta launch of one-click integrations with two telephony partners: AudioCodes

SignalWire

March 31, 2020

When using fulfillment, the WebhookResponse.payload field can now only be used for two cases: Custom data sent from your webhook service to a Dialogflow API caller.

Google Assitant integration custom payload rich response messages. For all other custom payload rich response messages, you should use the WebhookResponse.fulfillment_mesages[].payload field.

March 27, 2020

The shutdown of the V1 API announced in November has been extended to May 31, 2020,

March 13, 2020

March 10, 2020

Event names are now limited to 150 characters.

February 19, 2020

GA (general availability) launch of versions and environments.

GA (general availability) launch of agent validation.

You can now update fulfillment settings with the API. For more information, visit the agent reference and click the link for your protocol or client library language.

January 31, 2020

Beta launch of mega agents to combine multiple sub-agents agents into a single mega agent.

January 06, 2020

The following integrations are now deprecated and will be shut down on April 6th, 2020 May 6th, 2020 June 6th, 2020 July 6th, 2020 : Kik

Skype

Spark

Twilio IP Messaging

Twilio (Text Messaging)

Twitter

Viber Your live bots that use these integrations will stop working unless you take action. The implementations of these integrations have moved to open source. To continue using these integrations, follow the instructions at the GitHub repository.

December 19, 2019

If you use the Telegram integration, and the bot was created before August 19th, 2019, you must restart the integration in the Dialogflow console by February 28th, 2020. To restart it, perform the following steps for all your agents that use Telegram: Make sure you don't change or delete your current token on the Telegram side. Open the agent in the Dialoglow Console. In the integration settings, click the STOP button. Then click the START button.

December 04, 2019

You can now use Mutual TLS authentication to ensure that webhook traffic is both secure and trusted.

The Cortana exporter has been removed from the console.

November 14, 2019

We are extending the V1 API shutdown deadline to March 31st, 2020 May 31st, 2020. Migrate to the V2 API as described here. If you use Dialogflow exclusively for Actions on Google, you don't need to migrate your agent to the V2 API. However, note the following changes: The Dialogflow simulator will show responses in the V2 format and the "Copy curl" button will generate requests in the V2 format. This should have no impact on the functionality of the Actions on Google simulator.

You will no longer be able to call API methods for the V1 intents and entities resources. You will still be able to modify your agent using the Dialogflow Console.

October 17, 2019

When calling the API to provide an intent priority value, the behavior has changed to the following: If the supplied value is unspecified or 0, the service translates the value to 500,000, which corresponds to the Normal priority in the console.

priority in the console. If the supplied value is negative, the intent is ignored in runtime detect intent requests. Prior to this change, a value of 0 was stored as-is by the service. Any agents created before this change may still have intent priority values of 0. For runtime detect intent requests, a value of 0 is treated as -1, and the intent is ignored.

October 01, 2019

You can now create session entities with fulfillment.

You can now disable automatic agent training. See the ML settings for details.

September 20, 2019

Beta launch of Agent Validation to check your agent for quality and correctness.

September 19, 2019

You can now use System entity extension to extend system entities with custom values.

September 13, 2019

You can now use Regexp entities to provide regular expressions for matching entities.

You can now use Fuzzy matching to allow flexibility with word ordering for multi-word entities.

July 23, 2019

Beta launch of Auto speech adaptation to improve the speech recognition accuracy of your agent.

June 13, 2019

You can now create and update agents with the API. See the Agents type reference.

May 23, 2019

GA (general availability) launch of Speech response.

GA (general availability) launch of Sentiment analysis.

Pricing and Quotas have been updated for speech response and sentiment analysis.

All REST command line samples in documentation now include both curl (Linux, macOS) and PowerShell (Windows) commands.

May 15, 2019

Integration with Hangouts Chat is now supported.

April 18, 2019

The new @sys.person system entity has been added to all languages except Portuguese and Ukrainian. It is used for given names, last names, or their combinations. You should start using @sys.person instead of the existing @sys.given-name and @sys.last-name system entities.

January 15, 2019

Added support for Polish, including new system entities and pre-defined follow-up intents.

December 18, 2018

Added support for Turkish, including new system entities and pre-defined follow-up intents.

You can no longer annotate training phrases with some locale-specific entities. These entities are marked as deprecated in the system entities documentation. However, if you already have training phrases annotated with these entities in your existing agents, they will continue to function properly.

December 04, 2018

Template mode has been deprecated. Example mode is the only supported way to create new training phrases. If you have existing training phrases that you've created in template mode, those will continue to work. For more information, see Example and template modes

September 20, 2018

Added zh-TW machine learning support.

August 09, 2018

The Dialogflow Enterprise Edition Plus pricing plan is now available. See Editions for details.

July 24, 2018

Beta launch of Adding Speech Response to Detect Intent Requests

Beta launch of Adding Sentiment Analysis to Detect Intent Requests

Beta launch of Knowledge Connectors

Beta launch of Telephony Gateway

Beta launch of Data Logging and Enhanced Speech Models

Beta launch of Automatic Spell Correction

May 08, 2018

The Versions and Environments beta feature has launched.

You can now enable and view Stackdriver logs for your fulfillment.

When a phrase is matched to an intent when it shouldn't be, you can now designate it as a negative example and add it to the Default Fallback Intent.

The following geography system entities have been added to pt-BR, Nl, Ko, Hi, Id, Th, No, Sv, and Da languages: @sys.geo-country, @sys.geo-city, and @sys.geo-capital.

April 17, 2018

The Dialogflow V2 API is now GA (general availability). See the GCP blog post for details. Users of the V2beta1 API are encouraged to migrate to the V2 API. See Migrating code from Dialogflow V2beta1 to V2 for instructions. The V2beta1 API will continue to be a beta channel for the stable V2 API. If you plan to continue using V2beta1, see the migration instructions which describe how enabling ML will become the default.

March 29, 2018

We added additional system entities for the following languages: Hindi (hi)

Thai (th)

Indonesian (id)

Swedish (sv)

Danish (da)

Norwegian (no)

February 22, 2018

We added additional support for these languages: Hindi (hi)

Thai (th)

Indonesian (id)

Swedish (sv)

Danish (da)

Norwegian (no) We added ML support for these languages: Brazilian Portuguese (br-PT)

Korean (ko)

Dutch (nl)

December 01, 2017

We added new prebuilt agents: banking, easter egg, mobile account, and online shopping

We updated these prebuilt agents: flights (added FAQ) and profile bot (renamed to "Job Interview").

November 16, 2017