Once you deploy your conversation fulfillment, you can test out your Action on physical hardware devices or the Actions simulator. Dialogflow users can additionally test the different components of their Action using the guidance in Testing best practices.
Before you submit
Before submitting your Action for approval, we recommend you go through a pre-launch checklist. Using a checklist catches a lot of the issues we see during the approval process, and improves your project's chances of approval. Every subsequent time you update the Action package after submission, it must go through another approval cycle.
If you developed your Action using Dialogflow, consider using Dialogflow versioning to create an immutable version of your Dialogflow agent prior to Action submission. This approach gives you to ability to create multiple versions of your Dialogflow agent, publish them to separate environments, and roll back to previous versions if necessary.
If you developed your Action using the Actions SDK, upload your finalized Action package to your Actions project:
gactions update --action_package PACKAGE_NAME --project PROJECT_ID
Submit for approval
When you're ready to submit your Action for approval, go to the Actions console and select your project. From the main navigation, go to Deploy. In each section, fill out the required information. More information about the various options and fields are available in Publish your Actions.
Finally, publish your project to one of the available channels on the Release page. More information about the various options and release environments are available in the releases documentation.
If you developed your Conversational Action using Dialogflow, you can also submit your Action from the Dialogflow Console. In the Dialogflow Console, go to Integrations, then click Google Assistant. On the page that appears, click Manage Assistant App to go to the Actions console.
Dialogflow versioning FAQ
How does Dialogflow versioning impact my existing Actions?
Existing Actions submitted to the Actions Console prior to May 8, 2018 are not impacted. This means that edits you make to your Dialogflow agent continue to be reflected in the existing Action. If the Action is already published, the edits continue to be reflected live.
Will there be two versions I need to maintain in Action on Google and Dialogflow?
No, you have only one version as shown in your Manage releases page. It is unified across Actions on Google and Dialogflow. The only difference is now that we will create a snapshot of your Dialogflow agent at the time of submission. This snapshot will not be impacted by any future edits you make to your Dialogflow intents and entities.
Can I create and deploy Actions on Google versions from the Dialogflow Console?
No, you can only do so via the Actions Console.
In the Dialogflow page I saw that this is available for users who opt-in to beta, is that applicable for Actions on Google?
No, the Dialogflow beta program is for Dialogflow agents that are not on the Actions on Google platform. If you have a Dialogflow agent for the Actions on Google platform, then it is automatically enabled and not in beta.
What happens if I enable beta in the Dialogflow Console?
Doing so does not change Actions on Google projects. If you enable beta, you see an Environment tab in the Dialogflow Agent settings. In that page, you can view (but not edit) the same versions you created from the Actions Console and load any specific ones into the draft.
What is the suggested best practice for using alpha/beta/production releases with Cloud Functions for Firebase?
Dialogflow's inline editor does not have versioning for Cloud Functions for Firebase. However, each Dialogflow version points to custom webhook parameters. If you want to test different server logic with Alpha/Beta releases, we recommend that you turn off the inline editor, deploy your solutions into two Cloud Functions and pass those as webhook parameters in Dialogflow.