Google Sheets

Google Sheets is a web-based application that enables users to create and update spreadsheets in real time.

Google Sheets integration will generate tables containing data related to metadata and the individual sheets within a spreadsheet.

See the Schema section for a list of objects available for replication.

A high-level look at this connector, including useful links, and supported features.

Feature/Capability	Support details
Supported Qlik Talend Data Integration projects	Replication projects only. Data pipeline projects are not supported.
Target update methods	Replication tasks: Apply changes Store changes Landing data in a data lake tasks: Change data capture (CDC)
Managing metadata	Manual metadata generation is not required.
Schema evolution	Only the Change column data type operation is supported.
Replication of LOB columns (NCLOB, CLOB, and BLOB)	Not supported.
Scheduled CDC	Required. This is how the target is kept up-to-date with changes to the source. For replication tasks, see Scheduling tasks For lake landing tasks, see Scheduling CDC for lake landing tasks
Notifications	Partially supported Setting notifications for changes in operation
Monitoring	CDC-only, as full load is not relevant for this connector. Monitoring an individual data task
Automatic denesting of JSON column payloads	Not supported. JSON column payloads in source datasets are not denested automatically on the target.

Preparing for authentication

To access your data, you need to authenticate the connection with your account credentials.

Make sure that the account you use has read access to the tables you want to fetch.

The Admin access persmission is required in your Google Search Console account to change settings required for the connection. To obtain your client ID and secret:

Log into your Google Search Console account.
Create or select a project.
Select the Credentials tab on the left.
Select your OAuth app in the OAuth 2.0 Client IDs section. The client ID and secret are displayed.
Make sure Authorized Redirect URIs is set to https://connector.qlik.com/auth/oauth/v3.htm.
To create a new client ID, click Create Credentials.

Creating the connection

For more information, see Connecting to SaaS applications.

Click Authenticate when you have filled in the required connection settings.
You may be asked to log in to the source application.
A window is displayed with an authentication code.
Copy the code to the clipboard and return to the connection dialog.
Paste the code in Complete authentication with the code provided by the source and click Verify.
Tip noteYou may need to scroll down to see this field.
When status is Verified, the authentication is verified.
Provide a name for the connection in Connection name.
Select Open connection metadata to define metadata for the connection when it has been created.

Connection settings
Setting	Description
Data gateway	Select a Data Movement gateway if required by your use case. Information note This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None. For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.
Start Date	Enter the date, in the format `MM/DD/YYYY`, from which the data must be replicated from your source to your target.
Spreadsheet ID	The part of the URL when viewing or editing a Google sheet. Example: `https://docs.google.com/spreadsheets/d/SPREADSHEET_ID/edit?gid=SHEET_ID#gid=SHEET_ID` For more information, see the Google documentation.
Client ID	Client ID.
Client Secret	Client secret.

Schema

Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.

The schema and info displayed below is for version 1.

Depending on your destination, table and column names may not appear as they are outlined below.

file_metadata

The file_metadata table contains metadata about the spreadsheet defined in the integration’s settings.

Replication Method	CDC
Primary Key	id
Replication Key	modifiedTime
Useful links	Google Sheets documentation Google Sheets API method

createdTime

DATE-TIME

driveId

STRING

lastModifyingUser

OBJECT

This is a nested data structure:

displayName: STRING
emailAddress: STRING
kind: STRING

modifiedTime

DATE-TIME

name

STRING

teamDriveId

STRING

version

INTEGER

sheet_metadata

The sheet_metadata table contains metadata about the sheets within the spreadsheet defined in the integration’s settings.

Replication Method

Full Table

Primary Key

sheetId

Useful links

Google Sheets documentation

Google Sheets API method

columns

ARRAY

This is a nested data structure:

columnIndex: INTEGER
columnLetter: STRING
columnName: STRING
columnSkipped: BOOLEAN
columnType: STRING
format: STRING
type: ARRAY, which is also a nested data structure.

gridProperties

OBJECT

This is a nested data structure:

columnCount: INTEGER
frozenColumnCount: INTEGER
frozenRowCount: INTEGER
rowCount: INTEGER

index

INTEGER

sheetId

INTEGER

sheetType

STRING

sheetUrl

STRING

spreadsheetId

STRING

title

STRING

sheets_loaded

The sheets_loaded table contains metadata about individual sheets loaded to your destination.

Replication Method

Full Table

Primary Keys

sheetId

spreadsheetId

loadDate

Useful links

Google Sheets documentation

Google Sheets API method

lastRowNumber

INTEGER

loadDate

DATE-TIME

sheetId

INTEGER

spreadsheetId

STRING

title

STRING

spreadsheet_metadata

The spreadsheet_metadata table contains metadata about the spreadsheet defined in the integration’s settings.

Replication Method

Full Table

Primary Key

spreadsheetId

Useful links

Google Sheets documentation

Google Sheets API method

properties

OBJECT

This is a nested data structure:

autoRecalc: STRING
locale: STRING
timeZone: STRING
title: STRING

spreadsheetId

STRING

spreadsheetUrl

STRING

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here