Gives you an introduction to the Cloudpress Google Docs Add-On which you can use to export content to your blog or website
The Google Docs Add-on allows you to export documents using Cloudpress without leaving the Google Docs Editor.
Open the Marketplace
Open the Google Workspace Marketplace by opening a Google Doc and selecting the Extensions > Add-ons > Get add-ons item from the menu.
Search for Cloudpress add-on
Search for Cloudpress using the search box at the top and selecting the Cloudpress add-on
Install the add-on
Install the add-on by clicking on the Install button.
If you are using a Google Workspace account, the Install option may be replaced with
Accept permissions
Cloudpress requires certain permissions to export content. During the installation process, Google will prompt you to accept these permissions. Click the Allow button to proceed.
You must configure the Add-on with your personal access token before you can export content.
Copy your Personal Access Token
Go to your User Profile and copy your Personal Access Token to the clipboard.
Open Add-on
Open the Cloudpress Google Docs Add-on by clicking on the Cloudpress icon in the side panel.
Configure Add-on
You will be prompted to configure the Cloudpress Add-on. Click the Update Settings button. Paste the personal access token you previously copied into the Personal Access Token textbox, and click the Save button.
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.
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.
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.
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”.
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.
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.
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.
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.
When using the Google Docs Add-on, you may run into issues. This document hopes to address the most common issues.
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:
We think the first option will likely be the least disruptive to your workflow.
Gives you an introduction to the Cloudpress Google Docs Add-On which you can use to export content to your blog or website
The Google Docs Add-on allows you to export documents using Cloudpress without leaving the Google Docs Editor.
Open the Marketplace
Open the Google Workspace Marketplace by opening a Google Doc and selecting the Extensions > Add-ons > Get add-ons item from the menu.
Search for Cloudpress add-on
Search for Cloudpress using the search box at the top and selecting the Cloudpress add-on
Install the add-on
Install the add-on by clicking on the Install button.
If you are using a Google Workspace account, the Install option may be replaced with
Accept permissions
Cloudpress requires certain permissions to export content. During the installation process, Google will prompt you to accept these permissions. Click the Allow button to proceed.
You must configure the Add-on with your personal access token before you can export content.
Copy your Personal Access Token
Go to your User Profile and copy your Personal Access Token to the clipboard.
Open Add-on
Open the Cloudpress Google Docs Add-on by clicking on the Cloudpress icon in the side panel.
Configure Add-on
You will be prompted to configure the Cloudpress Add-on. Click the Update Settings button. Paste the personal access token you previously copied into the Personal Access Token textbox, and click the Save button.
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.
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.
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.
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”.
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.
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.
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.
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.
When using the Google Docs Add-on, you may run into issues. This document hopes to address the most common issues.
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:
We think the first option will likely be the least disruptive to your workflow.