Push your Action project to the Actions console with OVAI & gactions CLI

Typically Google Assistant Actions leverage Dialogflow to manage fulfillment and the interaction model for your Action.  There is a way to build an Action without Dialogflow, allowing you to bring your own NLU.

Prerequisites 

• An Actions project created
• OVAI CLI installed
  • See instructions here
• gactions CLI installed 
  • See instructions here

Pushing your Action

You must first create an action package that will be uploaded to your Actions project.  An action package is simply a JSON file describing your Action.

From the command line:

ovai push -p g -a {appId} -o {output directory}

For example, to push an app with ID app-id that will save the package file to your current directory:

ovai push -p g -a app-id -o .

Then using the gactions CLI, push the actions.json file from the previous step:

gactions update --project {actionsId} --action_package {path to actions.json}

Note: The gactions CLI may ask you to authenticate (sign-in) to your Google account.  Follow the instructions and make sure you select the account that has access to the Action you are going to push to.  When you authenticate, it will save a creds.data file to your the current directory you ran the command from.  These are powerful credentials and must not be shared or checked in to any repository.