Deploying a Google action

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
For those paying attention, you would have probably noticed that Google's conversational actions are already being deprecated. A little bit unclear what the exact reasoning is, but it seems Google wants to drive more on structured data than individua...
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

Now that we have our Google Action fully functional, we can look at deploying it so that it will become active for everyone.
I've never done this before, so bear with me, as Google might come back and reject the action for some reason.
First of all, head over to your Google actions console and ensure you tested the app on all possible devices in the Test tab.
Once you are ready to deploy, head over to the deploy tab. In this tab, you'll find a small overview of the most important parts with a detailed option on the left.

I started filling out the information on this page, and here are the required fields:
Let me dive a little bit deeper into the Privacy policy as it's the one that might require some more work.
If you already have a generic one on your website, you can use that. If you don't have one, you can use a free tool like TermsFeed to generate one.
You can then follow Google's actions example of hosting it on Google Drive and making the link publicly available. They do an excellent job of explaining how it works inside the privacy policy step.
Mine looks like this: Google action privacy policy.
And once that's all filled out, head over to the release section in the left-side menu. From here, you can start a new release by clicking the button. Your version will be 1, and you can select "production" as your channel.
Check that you have gone through all the steps described and want to do a full rollout.

Once done, you'll either be prompted that it succeeded or missed a step somewhere. You can simply go back and fix it and try again.
In the end, your submission will be visible in the release section, and you should receive an email about this.

Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter