The Cloudpress Google Docs Add-On

​

Introduction

The Google Docs Add-on allows you to export documents using Cloudpress without leaving the Google Docs Editor.

​

Install the Add-on

​

Configure your personal access token

You must configure the Add-on with your personal access token before you can export content.

​

Export a document

For details on exporting a document with the Google Docs Add-on, please review the Export Google Docs to your CMS (using Google Docs Add-On) documentation.

​

Configure additional Add-On settings

Open the Cloudpress Google Docs Add-on by clicking on the Cloudpress icon in the side panel.

Click on the three dots menu icon in the top right corner, then click Settings.

​

1. Personal Access Token

The personal access token is required for the Add-on to communicate with the Cloudpress application. You can obtain your personal access token from your User Profile.

​

2. Suggestions

Determines how Cloudpress should handle suggestions from other collaborators (which you have yet to accept or decline) when exporting the document. Let’s take the following example where a collaborator has suggested replacing the word “correct” with “wrong”.

• Export without suggestions: All suggestions from collaborators are ignored. In the example above, Cloudpress will export the text “This is correct”.
• Export with suggestions inline: All suggestions from collaborators are exported along with the original text. In the example above, Cloudpress will export the text “This is wrongcorrect”.
• Export with suggestions accepted: All suggestions are deemed to be accepted and exported instead of the original text. In the example above, Cloudpress will export the text “This is wrong”.

​

3. Use property table

The setting allows you to use a property table to set additional fields in your CMS when exporting content. This is useful when you want Cloudpress to update additional field values on your behalf, for example, the author or category of a blog post. You can find a detailed explanation of this feature in our documentation on setting additional field values with the Google Docs Add-on.

​

4. Auto-detect embeds

When this option is enabled, Cloudpress will attempt to convert standalone links in a single paragraph to the appropriate embed in your CMS. For example, if you have a paragraph containing only a link to a tweet, Cloudpress will convert it to the correct embed when exporting the document to your CMS.

​

5. Convert single-cell tables to code blocks

This option is useful when you want to include programming code snippets in your content. When enabled, Cloudpress will convert any single-cell table (i.e. a table with one row and one column) to a code block when exporting the document to your CMS.

​

6. Treat single-cell tables with a dotted border as raw content

Enabling this option will treat a single-cell table with a dotted border as raw content. This means that the content inside that table will be sent to your CMS as-is. This allows you to export content to your CMS that is not supported by Google Docs, for example exporting a custom Gutenberg block to WordPress. Please refer to our documentation on exporting custom content.

​

Troubleshooting

When using the Google Docs Add-on, you may run into issues. This document hopes to address the most common issues.

​

Authorization is required to perform that action

One of the most common issues you may encounter is the error message “Authorization is required to perform that action”.

This error is related to the way Google handles users being signed in with multiple Google accounts. There is an issue logged in the Google Issue Tracker, but unfortunately, this is not an error we can fix. It is up to Google to fix this error.

At this time, we can offer the following three options as workarounds:

1. Configure multiple user profiles in Chrome and sign into a single Google account per user profile (see the Chrome docs for more information).
2. Sign out of your other Google accounts and only sign in to the account you want to use Cloudpress with
3. Use your web browser’s Incognito (or private) mode (see the Chrome docs for more information).

We think the first option will likely be the least disruptive to your workflow.