Google Spreadsheets component

A Google Spreadsheets component to read and write to the Google Spreadsheet.

Latest changelog

1.2.2 (September 6, 2020)

Add request rate limits handling

To see the full changelog please use the following link.

Requirements

Google preparations

Before building any integration flow you must at first configure the app from inside the Google Developers Console.

In order to do this you, go to the API & Service page and enable the following:
- Google Drive API
- Google Sheets API
Go to the Credentials section and create a new credential of type OAuth client ID.
- Set Application type to Web application
- Add Authorized redirect URI as: https://{your-tenant-address}/callback/oauth2

In case of new domain you may get message like This app isn't verified. Please refer to this doc to check how to proceed: https://support.google.com/cloud/answer/7454865?hl=en

Environment variables

Here are the environment variables to configure for the component to connect with the Google API:

Following environment are required:

OAUTH_CLIENT_ID - oauth App ID
OAUTH_CLIENT_SECRET - oauth App Secret
TENANT_DOMAIN - your Google API tenant domain
LOG_LEVEL - trace debug info warning error controls logger level
REQUEST_TIMEOUT_PERIOD - If you want to slow down requests to your API you can set delay value (in ms) and the component will delay calling the next request after the previous request. Time for the delay is calculated as REQUEST_TIMEOUT_PERIOD/ REQUEST_TIMEOUT_QUOTA and shouldn’t be more than 1140 seconds (19 minutes due to platform limitation). The current values of this variables can be found in Google documentation. The REQUEST_TIMEOUT_PERIOD value by default is 100000 (100 sec).
REQUEST_TIMEOUT_QUOTA - the field can be used in pair with REQUEST_TIMEOUT_PERIOD, default to 500.

Please note: if result quota restriction will be less than 1 request/min component Retrieve Sample task won’t be complete

To get these please use the Google Developers Console. As a callback please use https://your-tenant.address/callback/oauth2.

Recommended environment variable:

EIO_REQUIRED_RAM_MB - recommended value of allocated memory is 512 MB

Completeness Matrix

The component completeness matrix gives the technical details about Salesforce objects this component covers.

Credentials

Google Spreadsheet works with OAuth2 app configured at your Google Developer Console. To Authenticate the component you only need to press the button Authentication and the process would take you to Google to log-in and give permissions to the platform to access your Spreadsheets.

Triggers

Google Spreadsheets component includes the following triggers:

Get Spreadsheet Row trigger The New Spreadsheet Row trigger reads the data in each row of a given Google Spreadsheet and passes it to the next stage of your integration flow.

The following Google Spreadsheets triggers are deprecated:

Rows(deprecated) Trigger is deprecated - please use Get Spreadsheet Row trigger. The Rows trigger reads the data in each row of a given Google Spreadsheet and passes it to the next stage of your integration flow.

Actions

Google Spreadsheets component includes the following actions:

Create New Spreadsheet action
Action to create a new Google spreadsheet.
Add Spreadsheet Row action
Action to create a new Google spreadsheet row.
Add Row(deprecated) action
This action is deprecated - please use Add Spreadsheet Row action.

Recommendations

Here are some general recommendations to help you avoid potentially confusing cases where you might get unexpected results while using Google Spreadsheets connector.

Spreadsheet Country Format

Depending on your Google Account settings your Google Drive and especially Google Spreadsheets would have some specific default formatting applicable to the Account Language/Country Setup in use. By default, Google will assume US formatting which would mean not only the default currency is US Dollar ($) but also, the date format will be of MM/DD/YYYY format, not DD/MM/YYYY which is widely used in European and other countries.

Google Spreadsheet default Language Settings

Please note if the data you are planning to write has values in different language/country formatting than your Google Spreadsheets then you are most likely to encounter unexpected results.

Make sure to change it to the desired one in the Google Spreadsheets in advance by selecting File > Spreadsheet Settings ... menu of your Spreadsheet.

Changing the Spreadsheet structure

Do NOT change the Spreadsheet structure while your flow is active

If you make structural changes to the Google Spreadsheet while it is being used it will cause a number of Errors and the flow will stop functioning properly.

Decide the structure of your spreadsheet file in advance and avoid making any structural changes during the integration. In particular, avoid adding or removing additional columns since you would need to repeat the flow design process to properly map or link your changes.

If you still wish to change the structure of your Google Spreadsheet then follow these steps:

Stop the integration flow if it is running;
Make your changes in the Google Spreadsheet;
Go through the integration design stage again to ensure that all columns in the modified spreadsheet are properly linked with required fields or values necessary to run your integration flow.
Activate the flow again.

Inserting a row

Do NOT insert a row between the records while your flow is active

If you insert a new row between existing structure the system would fail to recognize it as an update. Instead, this will cause the system to lose the connection between the unique IDs and the records since our unique ID is the row number.

If you wish to insert a row between existing records then you must first stop the integration flow in your Dashboard and then proceed to make the changes in your Google Spreadsheets file. You can activate your flow after you made the necessary changes. However, we recommend not to insert a row between the records even if you have deactivated it.

New inserted row will cause an additional data transfer

Avoid inserting a row in between the records during the integration since it would look different for the system. This would trigger an additional data transfer since not only the newly inserted row will be regarded as a new record but everything after the inserted row would be considered a new data.