Outbound Google Drive component
The Outbound Google Drive component provides a way to save files to Google Drive. It can also save new files from the exchange body of a flow.
Configuration
The Outbound 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, files will be saved in the root directory.
You can find the Directory ID in the browser URL when a Google Drive directory is open. It's the string after the last slash: .../drive/folders/<Directory ID>
Using Outbound Google Drive
To save the exchange body to a file, the CamelFileName header must be set. Make sure to add the correct extension, reflecting the data in your body. When a file is loaded into your flow, for instance with an Inbound Google Drive component, this header is set automatically. You can edit this header using a SetHeaders component.
Google Drive has a daily upload limit of 750 GB per user. While a single file larger than 750 GB can be uploaded, no additional files can be uploaded that day. For more details, refer to the Google Drive documentation.