Power BI Google Drive Connector

In this article you will learn how to integrate Google Drive data to Power BI without coding in just a few clicks (live / bi-directional connection to Google Drive). Read / write Google Drive data inside your app; perform many Google Drive operations without coding, just using easy to use high performance API Connector for Google Drive.

Using Google Drive Connector you will be able to connect, read, and write data from within Power BI. Follow the steps below to see how we would accomplish that.

Download Help File Buy

Driver mentioned in this article is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc.

If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started.

Video Tutorial - Integrate Google Drive data in Power BI

This video covers following and more so watch carefully. After watching this video follow the steps described in this article.

How to download / install required driver for Google Drive integration in Power BI
How to configure connection for Google Drive
Features about API Driver (Authentication / Query Language / Examples / Driver UI)
Using Google Drive Connection in Power BI

Create ODBC Data Source (DSN) based on ZappySys API Driver

To get data from GoogleDrive using Power BI we first need to create a DSN (Data Source) which will access data from GoogleDrive. We will later be able to read data using Power BI. Perform these steps:

Install ZappySys ODBC PowerPack.
Open ODBC Data Sources (x64):
Create a User Data Source (User DSN) based on ZappySys API Driver

ZappySys API Driver

You should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version.
When the Configuration window appears give your data source a name if you haven't done that already, then select "Google Drive" from the list of Popular Connectors. If "Google Drive" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

GoogleDriveDSN

Google Drive

Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

User Account [OAuth]

Steps to get Google Drive Credentials

To make this work you will have to create an OAuth application. To register an App, perform the following steps (Detailed steps found in the help link at the end):

Go to Google API Console
From the Project Dropdown (usually found at the top bar) click Select Project
On Project Propup click CREATE PROJECT
Once project is created you can click Select Project to switch the context (You can click on Notification link or Choose from Top Dropdown)
Click ENABLE APIS AND SERVICES
Now we need to enable Google Drive API.
Search Google Drive API. Select and click ENABLE
Go to back to main screen of Google API Console
Click OAuth Concent Screen Tab. Enter necessary details and Save.
Click Credentials Tab
Click CREATE CREDENTIALS (some where in topbar) and select OAuth Client ID option.
When prompted Select Application Type as Desktop App and click Create to receive your ClientID and Secret. You can use this information now to configure Connection with UseCustomApp=true.

Fill in all required parameters and set optional parameters if needed:

GoogleDriveDSN

Google Drive

User Account [OAuth]

https://www.googleapis.com/

Required Parameters
UseCustomApp	Fill in the parameter...
Optional Parameters
ClientId	Fill in the parameter...
ClientSecret	Fill in the parameter...
Scope	Fill in the parameter...
RetryMode	Fill in the parameter...
RetryStatusCodeList	Fill in the parameter...
RetryCountMax	Fill in the parameter...
RetryMultiplyWaitTime	Fill in the parameter...

Service Account (Using Private Key File) [OAuth]

Steps to get Google Drive Credentials
Use these steps to authenticate as service account rather than Google / GSuite User. Learn more about service account here

Basically to call Google API as Service account we need to perform following steps listed in 3 sections (Detailed steps found in the help link at the end)

Create Project

First thing is create a Project so we can call Google API. Skip this section if you already have Project (Go to next section)

Go to Google API Console
From the Project Dropdown (usually found at the top bar) click Select Project
On Project Propup click CREATE PROJECT
Once project is created you can click Select Project to switch the context (You can click on Notification link or Choose from Top Dropdown)
Click ENABLE APIS AND SERVICES
Now we need to Enable two APIs one by one (Drive API).
Search Drive. Select and click ENABLE

Create Service Account

Once Project is created and APIs are enabled we can now create a service account under that project. Service account has its ID which looks like some email ID (not to confuse with Google /Gmail email ID)

Go to Create Service Account
From the Project Dropdown (usually found at the top bar) click Select Project
Enter Service account name and Service account description
For Role, do not select anything for now and Click Continue and then click Done. Next we will create Key.

Create Key

Once service account is created we need to create key file (i.e. credentials).

In the Cloud Console, click the email address for the service account that you created.
Click Keys.
Click Add key, then click Create new key.
Click Create and select P12 format. A P12 key file is downloaded to your computer. We will use this file in our API connection.
Click Close.
Now you may use downloaded *.p12 key file as secret file and Service Account Email as Client ID (e.g. some-service-account-name@your-project-id.iam.gserviceaccount.com ).

Add Permission

Now last thing is give read/write permission to Service Account. Basically you can create or open Google Sheet and add the Service Account as an editor to it as below.

Copy the email address of your service account we created in previous step (its usually like this some-service-account-name@your-project-id.iam.gserviceaccount.com).
Create or select an existing Google Docs File.
Navigate to Google Docs File for which you like to give read/write access to Service Account.
Click on the Share button in the top right, and add the email address of the service account as an editor. Here is how to share file(s) with specific people. Juse share with Service Account (use Service Account Email found on previous section)

Fill in all required parameters and set optional parameters if needed:

GoogleDriveDSN

Google Drive

Service Account (Using Private Key File) [OAuth]

https://www.googleapis.com/

Required Parameters
Service Account Email	Fill in the parameter...
Service Account Private Key Path (i.e. *.p12)	Fill in the parameter...
Optional Parameters
Scope	Fill in the parameter...
RetryMode	Fill in the parameter...
RetryStatusCodeList	Fill in the parameter...
RetryCountMax	Fill in the parameter...
RetryMultiplyWaitTime	Fill in the parameter...

Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
Click OK to finish creating the data source.

Read Google Drive data in Power BI from ODBC

Once you open Power BI Desktop click Get Data to get data from ODBC:
A window opens, and then search for "odbc" to get data from ODBC data source:
Another window opens and asks to select a Data Source we already created. Choose GoogleDriveDSN and continue:

GoogleDriveDSN
Most likely, you will be asked to authenticate to a newly created DSN. Just select Windows authentication option together with Use my current credentials option:

GoogleDriveDSN
Finally, you will be asked to select a table or view to get data from. Select one and load the data!
Finally, use data extracted from Google Drive API in Power BI reports:

Import Google Drive data into Power BI from SQL Query

If you wish to import Google Drive data from SQL query rather than selecting table name then you can use advanced options during import steps (as below). After selecting DSN you can click on advanced options to see SQL Query editor.

Import Google Drive data into Power BI using SQL Query (ODBC Data source)

Edit Query / Using Parameters in Power BI (Dynamic Query)

In the real world, many values of your REST / SOAP API call may be coming from Parameters. If that's the case for you can try to edit script manually as below. In below example its calling SQL Query with POST method and passing some parameters. Notice below where paraAPIKey is Power BI Parameter (string type). You can use parameters anywhere in your script just like the normal variable.

let
    vKey=paraAPIKey,
    Source = Odbc.Query(
    "dsn=ZS-OData Customers", 
    "SELECT * FROM value WITH (SRC='http://httpbin.org/post'," 
    & "METHOD='POST'," 
    & "HEADER='Content-Type:application/json'," 
    & "BODY=@'{""CallerId"":1111, ""ApiKey"":""" & vKey & """}')")
in
Source

Edit Query Settings after Import

There will be a time you need to change initial Query after dataset import in Power BI. Not to worry, just follow these steps to edit your SQL.

Edit Power BI Data Source SQL after SOAP Web Service Import

Edit Power BI Data Source SQL after REST / SOAP Web Service Import

Using DirectQuery Option rather than Import

So far we have seen how to Import REST API data into Power BI but what if you have too much data and you dont want to import but link it. Power BI Offers very useful feature for this scenario. Its called DirectQuery Option. In this section we will explore how to use DirectQuery along with ZappySys Drivers. Out of the box ZappySys Drivers wont work in ODBC Connection Mode so you have to use SQL Server Connection rather than ODBC if you wish to use Live data using DirectQuery option. See below step by step instructions to enable DirectQuery mode in Power BI for REST API data. Basically we will use ZappySys Data Gateway its part of ODBC PowerPack. We will then use Linked Server in SQL Server to Link API Service and then we will issue OPENROWSET queries from Power BI to SQL Server and it will then call REST API via ZappySys Data Gateway.

Step-By-Step - How to query Google Drive API in SQL Server

First read this article carefully, How to query Google Drive API in SQL Server.
Once linked server is configured we are ready to issue API query in Power BI.
Click Get Data in Power BI, select SQL Server Database
Enter your server name and any database name
Select Mode as DirectQuery
Click on Advanced and enter query like below (we are assuming you have created JSON Data Source in Data Gateway and defined linked server (Change name below).
```
Select * from OPENQUERY(GOOGLE DRIVE_LINKED_SERVER,'SELECT * FROM Customers')
```
Select * from OPENQUERY(
GOOGLE DRIVE_LINKED_SERVER,
'SELECT * FROM Customers'
)

DirectQuery option for Power BI (Read REST API Data Example using SQL Server Linked Server and ZappySys Data Gateway)
Click OK and Load data ... That's it. Now your Google Drive API data is linked rather than imported.

Working with Gateways in Power BI (Schedule Import)

If the data needs to be updated, it is necessary to create a gateway on-premises. In this new section, we will install a Power BI Gateway and in the next section schedule it to update the REST API information.

In the last section, we Published the report. Power BI may ask you to SIGN IN.

Sign in Power BI
Select the Workspace and select Datasets

Go to workspace and dataset
Right-click the report and select Settings.

Specify settings for the report
The system will ask for a Gateway. Stay here.

Add Power BI Gateway

Use the following link to install a Data Gateway:

https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem

Run the installer and press Next

Gateway installer
Select the option On-premises data gateway (recommended). This option allows access to multiple users and can be used by more applications than Power BI.

Choose Power BI option
The installer will show a warning message.

Warning message during installation
Select the path to install and check the I accept the terms.

Accept terms
Specify the email address to use the gateway.

Register email address
After entering the email, write the gateway name and a recovery key. Make sure to confirm the recovery key.

Enter recovery key

Manage gateways and configure the schedule

Once that the gateway is installed we will configure it and add the connection strings.

The next step is to go to manage gateway

Power BI - Manage Gateway Setting
In order to get the connection string, we will need the connection string of the ZappySys JSON Driver. In the first section of this post, we explained how to configure it. Press Copy Connection String

Connection properties
Once that the data is copied, add a New data Source. In Data Source Name, enter the Data Source Name of the ZappySys JSON driver in step 13 and in Data Source Type, select ODBC. In connection string copy and paste from the clipboard of the step 13 and press Add.

ZappySys connection properties in Power BI
Once added the gateway. You can see the schedule refresh to On and Add another time to add the time where you want to refresh the data.

Schedule gateway

Create Custom Store Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Store Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
Enter the desired Procedure name and click on OK:
Select the created Store Procedure and write the your desired store procedure and Save it and it will create the custom store procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
```
CREATE PROCEDURE [usp_get_orders]
    @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
 AS
    SELECT * FROM Orders where OrderDate >= '<@fromdate>';
```
That's it now go to Preview Tab and Execute your Store Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
```
Exec usp_get_orders '1996-01-01';
```
Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
```
Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.

Create Custom Virtual Table in ZappySys Driver

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

Go to Custom Objects Tab and Click on Add button and Select Add Table:
Enter the desired Table name and click on OK:
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
```
SELECT
  "ShipCountry",
  "OrderID",
  "CustomerID",
  "EmployeeID",
  "OrderDate",
  "RequiredDate",
  "ShippedDate",
  "ShipVia",
  "Freight",
  "ShipName",
  "ShipAddress",
  "ShipCity",
  "ShipRegion",
  "ShipPostalCode"
FROM "Orders"
Where "ShipCountry"='USA'
```
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
```
SELECT * FROM "vt__usa_orders_only"
```
Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
```
Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.

Conclusion

In this article we discussed how to connect to Google Drive in Power BI and integrate data without any coding. Click here to Download Google Drive Connector for Power BI and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download Google Drive Connector for Power BI Documentation

Actions supported by Google Drive Connector

Google Drive Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.

Get drive info

Gets drive information

Search items

Lists items (i.e. files / folders) with search criteria

List folders

Lists folders

Parameter	Description
PageSize
Search Criteria

List files

Lists files

Parameter

Description

PageSize

Search Criteria

Data filter (e.g. somecolumn -eq 'somevalue' ) , User can select multiple filter criteria using 'AND','OR' operator , Note*:- please refer the link for more filter criteria : https://zappysys.com/links?url=https://developers.google.com/drive/api/guides/search-files

Option	Value
none
Allow only shared files and folders	sharedWithMe=true
Skip trashed files	trashed=false
Skip Folders	mimeType!='application/vnd.google-apps.folder'
Skip App Script	mimeType!='application/vnd.google-apps.script'
Search for file name	name='enter the filename here'
Search for full text	fullText contains 'enter the fullText here'
Search for spreadsheet	mimeType = 'application/vnd.google-apps.spreadsheet'
Search for multiple files type	mimeType contains 'application/vnd.google-apps.spreadsheet' OR mimeType contains 'application/vnd.google-apps.document' OR mimeType contains 'application/vnd.google-apps.presentation' OR mimeType contains 'application/vnd.google-apps.drawing'

List deleted files

Lists files

Parameter	Description
PageSize
Search Criteria

Get file info

Gets information of a file

Parameter	Description
Id	Id of a file you want to see information for

Download a file

Downloads a file

Parameter	Description
File Id	Id of a file you want to download

Export a file

Export a document editor files such document, Spreadsheets, Drawings, Presentations, Apps Scripts to common file formats as defined in this link https://developers.google.com/drive/api/guides/ref-export-formats

Parameter

Description

File Id

Id of a file you want to export and file must be editor type (e.g. document, Spreadsheets, Drawings, Presentations, Apps Scripts)

Export As (Mime Type)

The MIME type of the format requested for this export.

Option	Value
None
Export to PDF	application/pdf
Export to HTML	text/html
Export to HTML (zipped)	application/zip
Export to Plain text	text/plain
Export to Rich text	application/rtf
Export to Open Office doc	application/vnd.oasis.opendocument.text
Export to MS Word document	application/vnd.openxmlformats-officedocument.wordprocessingml.document
Export to EPUB	application/epub+zip
Export to MS Excel	application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Export to Open Office sheet	application/x-vnd.oasis.opendocument.spreadsheet
Export to (sheet only)	text/tab-separated-values
Export to JPEG	image/jpeg
Export to PNG	image/png
Export to SVG	image/svg+xml
Export to MS PowerPoint	application/vnd.openxmlformats-officedocument.presentationml.presentation
Export to Open Office presentation	application/vnd.oasis.opendocument.presentation
Export to JSON	application/vnd.google-apps.script+json

fields

Upload a file

Uploads a file

Parameter	Description
FileName	A filename the file will have in Google Drive
DiskFilePath	Specify a disk file path
ParentFolderId	Id of a parent folder you want to upload the file in. Use value 'root' to place the file in the topmost level.
KeepRevisionForever	Defines whether uploaded file has revisions
AddParents	A comma-separated list of parent IDs to add
OcrLanguage	A language hint for OCR processing during image import (ISO 639-1 code).
UseContentAsIndexableText	Whether to use the uploaded content as indexable text.

Create a folder

Creates a folder

Parameter	Description
Name	A folder name the folder will have in Google Drive
ParentFolderId	Id of a parent folder you want to create the folder in. Use value 'root' to create the folder in the topmost level.

Delete an item

Deletes an item

Duplicate a file

Duplicates a file

Parameter	Description
Id	Id of a file you want to duplicate

Update a file

Update file

Parameter	Description
Id	Id of a file you want to update
DiskFilePath	A disk file path you want to update file contents with
KeepRevisionForever	Defines whether uploaded file has revisions
AddParents	A comma-separated list of parent IDs to add
OcrLanguage	A language hint for OCR processing during image import (ISO 639-1 code).
UseContentAsIndexableText	Whether to use the uploaded content as indexable text.

Update metadata in a file

Updates meta-data in a file

Parameter

Description

Id of a file you want to update meta-data to

KeepRevisionForever

Defines whether uploaded file has revisions

Option	Value
True	True
False	False

AddParents

A comma-separated list of parent IDs to add

OcrLanguage

A language hint for OCR processing during image import (ISO 639-1 code).

UseContentAsIndexableText

Whether to use the uploaded content as indexable text.

Empty trash

Empties trash

Delete all items

Deletes all items from the drive

Generic Request

This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL.

Parameter	Description
Url	API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
Body	Request Body content goes here
IsMultiPart	Check this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter	Enter filter to extract array from response. Example: $.rows[] --OR-- $.customers[].orders[*]. Check your response document and find out hierarchy you like to extract
Headers	Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Other App Integration scenarios for Google Drive

SSIS

SQL Server

SSRS

Informatica

MS Access

MS Excel

SSAS

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (ADF)

ODBC

Other Connectors for Power BI

Zendesk

Azure DevOps

ManagedEngine ServiceDesk Plus (Zoho)

Zoho CRM

Hubspot

Google Sheets

Stripe

YouTube

Google BigQuery

OneDrive

OData

Amazon Ads

Mailchimp

Jira

Outlook Mail (Office 365)

Zoom

Cosmos DB

Shopify

Nativo

Google Drive

SharePoint Online

Amazon MWS

ServiceNow

ElasticSearch

Google Calendar

DropBox

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Download Google Drive Connector for Power BI Documentation

Common Searches:

How to connect Google Drive in Power BI?
How to get Google Drive data in Power BI?
How to read Google Drive data in Power BI?
How to load Google Drive data in Power BI?
How to import Google Drive data in Power BI?
How to pull Google Drive data in Power BI?
How to push data to Google Drive in Power BI?
How to write data to Google Drive in Power BI?
How to POST data to Google Drive in Power BI?
Call Google Drive API in Power BI
Consume Google Drive API in Power BI
Google Drive Power BI Automate
Google Drive Power BI Integration
Integration Google Drive in Power BI
Consume real-time Google Drive data in Power BI
Consume realtime Google Drive API data in Power BI
Google Drive ODBC Driver | ODBC Driver for Google Drive | ODBC Google Drive Driver | SSIS Google Drive Source | SSIS Google Drive Destination
Connect Google Drive in Power BI
Load Google Drive in Power BI
Load Google Drive data in Power BI
Read Google Drive data in Power BI
Google Drive API Call in Power BI

Power BI Google Drive Connector

How to Read/Write Google Drive data in Power BI

Power BI Google Drive Connector

Video Tutorial - Integrate Google Drive data in Power BI

Create ODBC Data Source (DSN) based on ZappySys API Driver

User Account [OAuth]

Service Account (Using Private Key File) [OAuth]

Create Project

Create Service Account

Create Key

Add Permission

Read Google Drive data in Power BI from ODBC

Import Google Drive data into Power BI from SQL Query

Edit Query / Using Parameters in Power BI (Dynamic Query)

Edit Query Settings after Import

Using DirectQuery Option rather than Import

Step-By-Step - How to query Google Drive API in SQL Server

Working with Gateways in Power BI (Schedule Import)

Manage gateways and configure the schedule

Create Custom Store Procedure in ZappySys Driver

Create Custom Virtual Table in ZappySys Driver

Conclusion

Actions supported by Google Drive Connector

Other App Integration scenarios for Google Drive

Other Connectors for Power BI

How to connect Google Drive in Power BI?

How to get Google Drive data in Power BI?

How to read Google Drive data in Power BI?

How to load Google Drive data in Power BI?

How to import Google Drive data in Power BI?

How to pull Google Drive data in Power BI?

How to push data to Google Drive in Power BI?

How to write data to Google Drive in Power BI?

How to POST data to Google Drive in Power BI?

Call Google Drive API in Power BI

Consume Google Drive API in Power BI

Google Drive Power BI Automate

Google Drive Power BI Integration

Integration Google Drive in Power BI

Consume real-time Google Drive data in Power BI

Consume realtime Google Drive API data in Power BI

Google Drive ODBC Driver | ODBC Driver for Google Drive | ODBC Google Drive Driver | SSIS Google Drive Source | SSIS Google Drive Destination

Connect Google Drive in Power BI

Load Google Drive in Power BI

Load Google Drive data in Power BI

Read Google Drive data in Power BI

Google Drive API Call in Power BI