Google Sheets Import

Installation

You can install this Google Workspace add-on here or directly from Google Sheets using this button in the sidebar:

After installing, click the Kontent icon in the sidebar to load the add-on's home page. Locate the following API keys in Kontent, then add them in the addon's Project settings menu,

• Project ID
• Preview API key
• Management API key

Preparing the Sheet

You may create a new Sheet or edit an existing one. The Generate Sheet menu of the add-on can also generate a new Sheet for you, along with the required headers, based on the project's content types.

If you have a local spreadsheet file, you can open it in Google Sheets by uploading it to Google Drive, then selecting Open with > Google Sheets.

Once the file is open in Sheets, you must re-save it as a Google Sheet file:

:warning: The name of the Sheet must match the code name of the content type in your project which will be used to create items

If you used the Generate Sheet menu to create the Sheet, the code name of the content type will be automatically generated. If you are creating the Sheet manually, you can find the content type code name in Kontent:

Setting the headers

The headers (first row) of your Sheet must contain the code names of the content type's elements. If you use the Generate Sheet menu of the add-on, these headers will be automatically generated. If adding headers manually, you can find the code names of the elements when editing the content type in https://app.kontent.ai.

In addition to the element code names, the header row can also contain these other headers:

• name (required): The name of the content item to create or update.
• __external_id__ (optional): The external ID of the content item to update.
• codename (optional): The codename of the content item being created/updated.
• language (optional): The language of the variant to update. This should match the code name of a language in the project’s Localization page, and is case sensitive. If a language is not provided, the add-on will get the project's default language using Management API.
• __currency_format__ (optional): Used to determine how values for Kontent "number" elements are parsed. US-formatted strings ("1,500.75") and EU-formatted strings ("1 500,75") are parsed into a valid number based on this setting. Should be either US or EU. If omitted or empty, US formatting will be used.
• rich_text_components (optional): JSON data of components used in all rich text elements of the row. See Components in rich text

:bulb: See the Locating and updating existing items section to read more about how existing items are located and how to update content item names and codenames.

The following is an example of what a Sheet named product might look like:

Formatting Cell Values

To avoid errors in importing data, the data in each column must be formatted according to the element it will be stored in. Most elements (such as Text and Number) are straight-forward, but some require specific formatting:

• Rich Text: See Setting Rich Text values
• Number: If the value is not a valid float like "12.50" the script will try to parse the number based on the __currency_format value (see Setting the headers). As US and EU formats are currently supported, some examples of valid numbers are: 1,500.75, 1.500,75, and 1 500,75. The cell should not contain letters or currency symbols.
  If you are using EU formatting, we recommend changing any Number columns in the Sheet to use Plain text__ formatting:

• Date & Time: The script will first try to parse the value using the JavaScript Date(string) constructor, so any valid DateTime string will succeed. A typical valid string would be in the format mm/dd/yyyy hh:mm am/pm. The script will also accept strings that use dashes instead of slashes (12-25-2019 6:00 AM) or timestamps from SQL (2019-12-25 06:00:00.0000000).
• URL Slug: There is no special formatting needed for URL Slug elements. If a value is provided, the element's mode will be changed to "custom" and no longer auto-generate based on another content type element. To revert the URL Slug element back to auto-generation, set the value to #autogenerate#.

• Taxonomy, Multiple Choice, Assets, Linked items: Values for these elements follow the same format: <identifier type>:<identifier> in a comma-separated list. The identifier can be id, codename, or external_id depending on the type of element. An example of multiple linked items in an element is codename:birthday_party,id:eba1015a-dfd4-5736-abc1-5de3ed5df732. You can find the supported reference types for each element in the Management API reference, or in the table below:	Element	Allowed references
  Asset	id, external_id
  Linked items	id, external_id, codename
  Multiple choice	id, codename
  Taxonomy	id, external_id, codename

Setting Rich Text values

This element will most likely require the most pre-processing; try to avoid complex HTML and text formatting. The list of supported HTML elements and their syntax can be found in the Management API reference. Notably, you can insert links to other content items or assets by referencing and ID or external ID using the format described in links in rich text.

For example: Buy our <a data-item-external-id="F4891FB5-5215-4795-8A6F-18A4F68394FD">new coffee</a>. You can also add inline content items using the supported syntax, for example <object type="application/kenticocloud" data-type="item" data-external-id="59713"></object>.

You can insert content item links, asset links, and inline content items by entering the HTML or macro manually. Or, you can use the Rich text macros menu found in the add-on to generate macros:

Components in rich text

You can use the rich_text_components column to store all components of a content item, regardless of how many Rich Text elements it contains. When exporting items from Kontent, the components are automatically generated. For example, if you have a Rich Text element that contains this component:

<object type="application/kenticocloud" data-type="component" data-id="382abced-bfb6-4ee9-a2d4-2c3b8cd8ba5d"></object>

then the rich_text_components must contain a component with that ID, or the import will fail. The format of components can be found in Management API reference. Using the above example, the rich_text_components value could look like this:

[{
  "id": "382abced-bfb6-4ee9-a2d4-2c3b8cd8ba5d",
  "type": {
    "codename": "article"
  },
  "elements": [
    {
      "element": {
        "id": "975bf280-fd91-488c-994c-2f04416e5ee3"
      },
      "value": "This is some text in the component"
    }
  ]
}]

You can use the Rich text macros menu to generate the JSON of a component if you don't wish to enter it manually. In this menu, you will select the content type of the component, and the elements of that type will appear. Once the values are populated, the macro and JSON are both generated:

Importing the Content

Click the Kontent icon in the sidebar and open the Import menu. You have two options before starting the import:

• Update existing items: If enabled, an existing content item will attempt to be updated using the external_id of each row, or the name if there is no external ID column. If you disable it, a new item will always be created, but be aware that you may run into errors if you’ve provided an external ID that already exists in the system. As is the case with all errors, the script will simply skip that record and continue processing the rest of the Sheet.

• Preload content items: If enabled, the script will load all content items from your project at the start. When attempting to locate existing items, the script will use the cached data, greatly reducing the number of API calls and execution time.

After clicking the Run button, please wait while the script runs. When it’s finished, a new window Sheet is created containing a detailed record of the operations taken per-row and general information:

Locating and updating existing items

Depending on what information is available in the sheet, existing items in your project are located differently. This is the order in which values are used to locate existing items:

1. __external_id__: If not found, a new item is created with this ID. For both new items and existing items found this way, you are able to update the name and codename of the content item if those values are present in the row.
2. codename: If not found, a new item is created with this codename. When updating existing items found this way, you can only update the name.
3. name: If not found, a new item is created with this name. For new items created this way, you can set the codename and external_id. If an existing item was found, you can only update the codename of the item.

Batching

The import process will run for a maximum of 30 seconds. If your Sheet contains a large amount of data that cannot be completed within 30 seconds, the import will be performed in batches. You will be shown a menu stating which rows were successfully processed, and you can click Resume to continue importing the Sheet.

Exporting items from Kontent

Using the Export menu, you can save your content items in Google Sheets, allowing you to create backups to import into the same project or even other projects. When you export your items, the add-on will generate a new Sheet for selected content type. Then, the Sheet will be populated with the content items of that type.

There is an optional Translate IDs setting you can enable before exporting. This add-on uses the Management API to retrieve your data, and references to objects like taxonomy, assets, etc. use the internal id of the object. If you enable this setting, the ID will be converted into either a codename or external_id if available.

This is helpful if you are considering exporting items from Project A and into Project B. Both projects may have a taxonomy term called "Events," but the id of the term will be different. If the codename is "events" in both projects, the content items which reference that taxonomy term can be imported without any issues.

Asset renditions

This add-on does't currently support exporting/importing asset renditions. Only the original asset reference will be exported to Google Sheets using this add-on.

Contributing

1. Clone this repo and run npm i
2. Create a Google App Script project
3. Run clasp login to connect the repo to your Google account
4. Make changes
5. Run npm run deploy to push changes to your App Script project
6. Test your changes with a Test Deployment in Google Sheets
7. Create a pull request to merge your changes