Google Drive Connector for UiPath
In this article you will learn how to integrate Using Google Drive Connector you will be able to connect, read, and write data from within UiPath. Follow the steps below to see how we would accomplish that. The driver mentioned above 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. |
Connect to Google Drive in other apps
|
Create ODBC Data Source (DSN) based on ZappySys API Driver
Step-by-step instructions
To get data from Google Drive using UiPath we first need to create a DSN (Data Source) which will access data from Google Drive. We will later be able to read data using UiPath. 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 DriverYou 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:
GoogleDriveDSNGoogle 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.
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. Later on you can use this information now to configure Connection with UseCustomApp=true.
NOTE: If you are planning to use your current data connection/token for automated processes, we recommend that you use a generic account for token generation when the login box appears (e.g. sales_automation@mycompany.com instead of bob_smith@mycompany.com). When you use a personal account which is tied to a specific employee profile and that employee leaves the company, the token may become invalid and any automated processes using that token will fail. Another potentially unwanted effect of using a personal token is incorrect logging; the API calls (e.g. Read, Edit, Delete, Upload) made with that token will record the specific user as performing the calls instead of an automated process.
- Go to OAuth Consent Screen tab. Under Publishing Status click PUBLISH APP to ensure your refresh token doesnt expire often. If you planning to use App for Private use then do not have to worry about Verification Status after Publish.
Fill in all required parameters and set optional parameters if needed:
GoogleDriveDSNGoogle DriveUser 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... Redirect URL (Only for Web App) Fill in the parameter... 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:
GoogleDriveDSNGoogle DriveService 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.
Video instructions
Read Google Drive data in UiPath Studio (workstation)
Here we will be reading Google Drive data on your workstation. To accomplish that we will create and run UiPath process package locally. Later on, we'll explore how to publish the package to Orchestrator and run it remotely. For now, let's focus on working locally and get started!
- Open UiPath Studio.
- Before we really begin the work, make sure UiPath Studio is set as your profile (blue application icon).
- In case, it is set to UiPath StudioX, you can change it in UiPath StudioX Settings: Simply select UiPath Studio option:
- Start by creating a new project based on UiPath Process template:
- Add Run Query activity in Main Sequence box:
- Click Configure Connection... button to create an ODBC connection:
- Continue by clicking Connection Wizard:
-
When the window opens, select ODBC-based driver, provider, and then choose ODBC data source:
GoogleDriveDSNGoogleDriveDSNYou can also select Use connection string option and use whole ODBC connection string instead. Obtain the connection string by pressing Copy Settings button in your data source configuration.
-
Once you do that, it's time to configure a SQL query:
Make sure, you enclose the query in double quotes!
-
Proceed by adding a Write CSV activity after Run Query:
In this article we are using Write CSV, but you can freely add any other destination of your choice, e.g. Write DataTable to Excel.
- Once you do that, configure the added Write CSV, this will write Google Drive data to a CSV file:
- It's time for fun! Which means it's time for debugging! Just run the package locally to debug:
- Finally, ensure there are no execution errors!
Run UiPath package using Orchestrator (via robot)
UiPath also offers the ability to execute packages remotely using Orchestrator and a robot. This is achieved by publishing the package to UiPath Orchestrator, installing UiPath Assistant on the remote machine, connecting it to Orchestrator, enabling us to run the package remotely. It may sound complicated at first glance, but further steps will clear things out. Let's not waste our precious time and delve into the details!
Publish process package from UiPath Studio
- First of all, open the UiPath process package we created in the previous step
- Set the option that our process package Starts in Background:
- We are ready to Publish it:
- Make sure, you publish it to the Shared folder in UiPath Orchestrator Tenant workspace:
- Finally, success! We are ready for the next step - creating UiPath robot - so we can automate the job:
Create robot in UiPath Orchestrator
- First of all, let's open UiPath Orchestrator from UiPath Automation Cloud console:
- It's time to create a robot, which will run unattended packages:
- But first we have to create a runtime. Choose to host our robot on-premise, not in UiPath infrastructure:
- Let's move along and Create new machine template, this will create a machine in UiPath Orchestrator:
- Configure the machine to run in Production environment:
- We are ready to Create new robot account in the new machine:
- Let's make our robot to work only on background automations:
- Continue by selecting newly created robot:
-
Select Shared folder, so that everyone in the team can benefit from it:
This is the folder where we published our UiPath process package "MyProcess"
- We are almost done! We are given machine Client ID and Client secret which we will use to connect UiPath Assistant to our created machine in Orchestrator. Let's leave this open for a while and see how we can do it in the next step.
Connect UiPath Assistant to Orchestrator
We are ready to connect UiPath Assistant to the machine we created in Orchestrator. UiPath Assistant will run our package in a remote machine. Let's connect it and give it some work!
- Connect to a remote machine (where your UiPath process package will be running).
- Install UiPath Studio there.
- Then configure ODBC data source:
If you chose Use user or system data source option in connection configuration, when creating UiPath process package, then create an identical ODBC data source on the same remote machine. Use the same configuration as the one created in your workstation in the first step.
Use Copy Settings and Load Settings buttons to make your life easier. They will help you to transfer settings between different ODBC data sources.If you chose Use connection string option, then you don't have to do anything. However, you still have to install ODBC PowerPack on the remote machine.
- Continue by opening UiPath Assistant and going to Preferences:
- Find Orchestrator Settings menu item and click it:
- And here even bigger fun begins! But fear not, all you have to do is open your web browser window with Client ID & Client secret we obtained in the previous step and simply copy and paste those values into UiPath Assistant. Also, don't forget to configure Orchestrator URL:
- Finally, we get rewarded for the hard work with the Connected as Unattended status:
Create and run UiPath process in Orchestrator
We are at the finish line! Let's create and run UiPath process. This will execute the package on your remote machine using the UiPath Assistant configured earlier.
- First of all, open UiPath Orchestrator from UiPath Automation Cloud console.
- Then proceed by going to Process in Shared folder:
- Continue by simply clicking on Add process button:
- Select the process package we created in UiPath Studio:
- Rest a while, and just hit Next, unless your package has requirements:
- Then simply hit Create button:
- But let's not stop here and Start the process by creating a job right away:
- Use the same Production runtime we created before and hit Start:
- We've reached the final step! In the CSV destination file or destination of your choice you should see Google Drive data:
Advanced topics
Create Custom Stored 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 Stored 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 Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored 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 Stored 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 stored 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 @fromdate=''1996-07-30''')
-
Now go to SQL served and execute that query and it will make the API call using stored 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.
If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.
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 stored 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 stored procedure and provide you the response.
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.Parameter | Description | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Search Criteria |
|
Parameter | Description | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Search Criteria |
|
Parameter | Description |
---|---|
Search Criteria |
|
Parameter | Description |
---|---|
Id |
|
Parameter | Description |
---|---|
File Id |
|
Parameter | Description | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
File Id |
|
||||||||||||||||||||||||||||||||||||||
Export As (Mime Type) |
|
||||||||||||||||||||||||||||||||||||||
fields |
|
Parameter | Description | ||||||
---|---|---|---|---|---|---|---|
Keep Revision Forever |
|
||||||
Parent FolderId |
|
||||||
Shared DriveId |
|
||||||
Drive Type |
|
||||||
Supports all drives (e.g. My and Shared) |
|
||||||
Target FileName |
|
||||||
Local FilePath |
|
||||||
AddParents |
|
||||||
OcrLanguage |
|
||||||
UseContentAsIndexableText |
|
Parameter | Description |
---|---|
Name |
|
Parent FolderId |
|
Parameter | Description |
---|---|
File Id |
|
Parameter | Description |
---|---|
File Id |
|
DiskFilePath |
|
KeepRevisionForever |
|
AddParents |
|
OcrLanguage |
|
UseContentAsIndexableText |
|
Parameter | Description | ||||||
---|---|---|---|---|---|---|---|
File Id |
|
||||||
Keep Revision Forever |
|
||||||
AddParents |
|
||||||
OcrLanguage |
|
||||||
UseContentAsIndexableText |
|
Parameter | Description |
---|---|
Url |
|
Body |
|
IsMultiPart |
|
Filter |
|
Headers |
|
Google Drive Connector Examples for UiPath Connection
This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.
Get my drive information [Read more...]
Gets my drive information
SELECT * FROM Drive
List all shared drives [Read more...]
List all shared drives
SELECT * FROM SharedDrives --WITH(Query='name = "HR"')
Get information about shared drive [Read more...]
Get information about shared drive
SELECT * FROM SharedDrives WITH(Query='name = "HR"')
List / search files from my drive [Read more...]
List or search files from my drive (use search query expression). Uncomment Query part to invoke filter
SELECT * FROM Files
WITH(
--Query='name contains "ZappySys*.*"', --includes files where name contains "zappysys" word
)
List / search files from a single shared drive [Read more...]
List or search files from a specific shared drive by driveId and search query expression. Uncomment Query part to invoke filter
SELECT * FROM Files
WITH(
--Query='name contains "ZappySys*.*"', --includes files where name contains "zappysys" word
DriveId='0AFWIggplk2z6Uk9PVA',
DriveType='drive',
SupportsAllDrives='true',
IncludeItemsFromAllDrives='true'
)
List / search files from all shared drives [Read more...]
List or search files from all shared drives by driveId and search query expression. Uncomment Query part to invoke filter
SELECT * FROM Files
WITH(
--Query='name contains "ZappySys*.*"', --includes files where name contains "zappysys" word
DriveType='allDrives',
SupportsAllDrives='true',
IncludeItemsFromAllDrives='true'
)
Dowload a file (my drive) [Read more...]
Downloads a file (from user my drive)
SELECT * FROM download_file
WITH(Id='1PpE2eSi5faAnMwiSolwr34zA5MwOdR3D'
,ResponseDataFile='C:\MyFiles\myfile.ext'
)
--You can get file Id by selecting from 'list_files' endpoint
Dowload a file from google shared drive [Read more...]
Dowload a file from google shared drive for which user has access
SELECT * FROM download_file
WITH(
DriveType='drive' --or set 'user' for mydrive
, DriveId='0AFWIggplk2z6Uk9PVA'
, Id='1hk7odj2Y2--yxN9DY0zW88hSnxqiyHq0' --file id
, ResponseDataFile='c:\temp\dump.zip'
--You can get file Id by selecting from 'list_files' endpoint
)
Upload local file to google shared drive folder [Read more...]
Upload a local file to google shared drive folder for which user has access. Donot set DriveId to upload to MyDrive rather than sahred drive.
SELECT *
FROM upload_file
WITH(
DriveId='0AC00HWQH144cUk9PVA' --team drive id (keep blank for uploading to my drive)
, DiskFilePath='C:\temp\dump.csv' --source file path
, FileName='dump.csv' --target file name
, ParentFolderId='1PRySfNNjWIp9ZAnhPh-u9tKRj3QOETSq'
, KeepRevisionForever='false'
)
Get file list [Read more...]
Downloads a file
SELECT * FROM Files
Update a file [Read more...]
Updates a file
UPDATE Files
WITH (Id='1EVzXFVBQIh3LcJvfcLhI1UWhW3qUxFkM'
,DiskFilePath='C:\MyFiles\myfile.ext')
--You can get file Id by selecting from 'list_files' endpoint
Delete a file [Read more...]
Deletes a file
DELETE FROM Files
WITH (Id='1gcu0hV34OTfgvcu9CFhr7Go4b35j5Mop')
--You can get file Id by selecting from 'list_files' endpoint
Delete a file by name from a shared drive [Read more...]
Delete a file by name from a shared drive
DELETE FROM Files where Name='dump.csv' and Trashed=0 WITH(DriveId='0AC00HWQH144cUk9PVA', DriveType='drive')
--You can get file Id by selecting from 'list_files' endpoint
Upload a file with INSERT keyword [Read more...]
Upload a file with INSERT keyword. Advantage of INSERT is you can use Bulk option using SOURCE clause. This way you can upload many files
INSERT INTO Files
WITH (FileName='My filename'
,DiskFilePath='C:\MyFolder\Mymyfile.ext'
,ParentFolderId='root'
)
--You can get ParentFolderId by selecting from 'list_folders' endpoint or just use 'root'
Delete a folder [Read more...]
Deletes a folder
DELETE FROM Folders
WITH (Id='1yDO11prsLH9DUrBTCadV6GGMJrITjF9I')
--You can get folder Id by selecting from 'list_folders' endpoint
Create a folder [Read more...]
Creates a folder
INSERT INTO Folders
WITH (Name='My folder name'
,ParentFolderId='root')
--You can get ParentFolderId by selecting from 'list_folders' endpoint or just use 'root'
Get file information [Read more...]
Gets file information
SELECT * FROM FileInfo
WITH (Id='1EVzXFVBQIh3LcJvfcLhI1UWhW3qUxFkM')
--You can get file Id by selecting from 'list_files' endpoint
Get items list [Read more...]
Gets items list
SELECT * FROM ItemsList
Get items list using query [Read more...]
Gets items list using query
SELECT Id, Kind, Name, MimeType
FROM list_items
WITH (Query = 'name contains ''.txt''')
Get files list [Read more...]
Gets files list
SELECT * FROM FilesList
Get folders list [Read more...]
Gets folders list
SELECT * FROM FoldersList
Select from trash [Read more...]
Shows deleted items in Trash
SELECT * FROM Trash
List files from trash for a shared drive [Read more...]
Shows deleted items in Trash
SELECT * FROM Trash
WITH(
DriveType='drive'
,DriveId='1j0HFOP4gsoExxxxxx' --get id from select * from SharedDrives
)
Empty trash bin [Read more...]
Empties trash bin
DELETE FROM Trash
Empty trash bin for a shared drive [Read more...]
Empties trash bin for a specified shared drive
DELETE FROM Trash
WITH(
DriveType='drive'
,DriveId='1j0HFOP4gsoExxxxxx' --get id from select * from SharedDrives
)
Export Google Sheet to Excel (xlsx) or PDF [Read more...]
Export a Google files to other format (e.g. Google Sheets to MS Excel / PDF)
SELECT "Status" FROM export_file
WITH(
Id='1j0HFOP4gsoE-Zbf2xN3IsPSj8wgwNtIfyyvM1_BWkW4' --//google sheet id or document ID
--,DriveId='xx your shared drive id' --get id from select * from SharedDrives
--,DriveType='drive'
, ExportAs='application/vnd.openxmlformats-officedocument.spreadsheetml.sheet'
--, ExportAs='application/pdf'
, ResponseDataFile='c:\temp\sheet1.xlsx'
, FileOverwriteMode='AlwaysOverwrite' -- or try 'FailIfExists' or 'SkipIfExists'
))
--You can export files from 'export_file' endpoint
Conclusion
In this article we discussed how to connect to Google Drive in UiPath and integrate data without any coding. Click here to Download Google Drive Connector for UiPath 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 UiPath
Documentation
More integrations
Other application integration scenarios for Google Drive
Other connectors for UiPath
Download Google Drive Connector for UiPath
Documentation
How to connect Google Drive in UiPath?
How to get Google Drive data in UiPath?
How to read Google Drive data in UiPath?
How to load Google Drive data in UiPath?
How to import Google Drive data in UiPath?
How to pull Google Drive data in UiPath?
How to push data to Google Drive in UiPath?
How to write data to Google Drive in UiPath?
How to POST data to Google Drive in UiPath?
Call Google Drive API in UiPath
Consume Google Drive API in UiPath
Google Drive UiPath Automate
Google Drive UiPath Integration
Integration Google Drive in UiPath
Consume real-time Google Drive data in UiPath
Consume real-time Google Drive API data in UiPath
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 UiPath
Load Google Drive in UiPath
Load Google Drive data in UiPath
Read Google Drive data in UiPath
Google Drive API Call in UiPath