Inbound Google Drive component
The Inbound Google Drive component provides an endpoint for loading Google Drive files into flows.
Configuration
The Inbound Google Drive component has the following configuration options:
Access Token
The access token that grants permission to connect to your Google Drive. Use @{myAccessToken}
to refererence your access token from the Tenant Variables.
The access token is cached. If the component reaches 60 failed connection attempts it will create a new 'client' and retrieve the access token from the Tenant Variables.
Refer to the SetOAuth2Token component page on how to set up access tokens.
Directory ID
The unique identifier of the folder where the component looks for files. If left blank, the root directory will be polled.
You can find the Directory ID in the browser URL when a Google Drive directory is open. It is the string after the last slash in the URL: .../drive/folders/Directory ID
.
File filter
A regex pattern can be specified to match the file names the component should retrieve.
Post process strategy
After a file is processed, you can choose to move it to a subdirectory of the folder being polled or delete it.
Options
Move
(default)Delete
Move to
Files will be moved to this subdirectory after processing, default: .dovetail
.
- Only available when Post process strategy is set to
Move
.
Initial delay
The delay (in milliseconds) before the component starts polling the Google Drive folder after a flow is installed.
Delay
The interval (in milliseconds) between each poll of the Google Drive folder.
G Suite files strategy
G Suite files (Docs, Sheets, Slides, etc) cannot be processed in the same way as regular files.
Options
Ignore
(default)Convert
Conversions
The component converts G Suite file types as follows:
Google Doc
⇢*.docx
Google Sheet
⇢*.xlsx
Google Slide
⇢*.pptx
Google Drawing
⇢*.jpg
It will fallback to PDF
whenever it's unable to find a compatible format.