Google Sheets CMS Integration

Learn how to use Google Sheets as CMS for your Alexa Skills and Google Actions.


With this Jovo CMS integration, you can manage all the content of your Alexa Skills and Google Actions in a Google Spreadsheet. This makes collaboration easier and enables you update and add content faster.

Here is what a sample spreadsheet could look like: Google Sheets CMS for Alexa and Google Assistant

You can use this Spreadsheet as a starter template.


To get started, install the following package:

Add it to your app.js file and register it with the use command:

Next, add configurations like the spreadsheetId to your config.js file:

Each sheet can be added as an object that includes both a name and a type. Learn more about Sheet Types below.

Additional configuration might differ depending if you want to use a publicly accessible or private spreadsheet:

Public Spreadsheets

Tutorial: Use Google Sheets as CMS for your Voice App

Public spreadsheets allow you to get started quickly whithout having to care about credentials. We recommend setting up a public spreadsheet first and then turning to private spreadsheets later.

For public spreadsheets, you need to add the following to your config.js file:

The additional information you need to add for public spreadsheets is the position of the sheet. It is the position of the tab the sheet is located in.

Private Spreadsheets

Tutorial: Use Private Google Spreadsheets as a CMS

With private spreadsheets, you can control who has access to your content. This comes with the price of a few more extra steps to set it up.

For private spreadsheets, you need to add the following to your config.js file:

To make private spreadsheets work, you need to create a service account and security credentials. These can be downloaded as a JSON file and then referenced in the credentialsFile element (default is ./credentials.json).

Default Sheet Types

Google Sheets offers flexible ways to structure data. This is why the Jovo CMS integration supports several sheet types that are already built in:


If you don't define a sheet type in the config.js, you receive an array of arrays that can be accessed like this:


If you define the sheet type as Responses, the integration expects a spreadsheet of at least two columns:

  • a key
  • a locale, e.g. en, en-US, or de-DE

For this locale, you can then access the responses like this:

You can add as many locales as you want by adding additional columns for each key.


If you define the sheet type as KeyValue, the integration expects a spreadsheet of at least two columns:

  • a key
  • a value

For every key, this will return the value as a string:


If you define the sheet type as ObjectArray, you will receive an array of objects where each row is converted to an object with the first row of the spreadsheet specifying the keys.

You can define the range (which columns to access) in your config:

Here's an example sheet:

Name Location Date
Voice Summit Newark, New Jersey, USA 7/22/2019
SuperBot San Francisco, California, USA 4/2/2019

And here's the array of objects you will receive:

Access the array using:

Defining your own Sheet Type

You can extend the Default sheet and pass it to the SpreadsheetCMS object like this:

You can then reference the sheet type by its name in the config.js file:

Advanced Features


The content of all sheets is cached into the Jovo app object by default, which allows for faster response times. For some use cases (like testing), however, it might make sense to retrieve the data for some (or all) sheets with every request. Since Jovo v2.1.4, we support these instant updates by setting the caching option to false.

You can choose between disabling caching for all sheets, or just specific ones in your config.js file:

Platform-specific Responses

Since Jovo v2.1.4 we support platform-specific responses for i18n, as well as for CMS. This allows you to have isolated output for a specified platform, without altering the default one.

Platform-specific Responses

In this example, the value for GOODBYE will be overwritten, whenever a response is triggered by an Alexa-Skill. WELCOME remains the same for all platforms. If you don't want any output for a specific platform, use /.

Comments and Questions

Any specific questions? Just drop them below or join the Jovo Community Forum.

Join Our Newsletter

Be the first to get our free tutorials, courses, and other resources for voice app developers.