Google Drive

Connect Google Drive when a team or partner keeps its documents there and needs Files.com's access methods or automated file exchange around them. A Mount exposes the remote content through a Files.com folder. A Sync transfers a separate copy between Google Drive and another location.

Google Drive's document types and naming model differ from a traditional file server. Native Google documents are exported into standard formats, and names do not uniquely identify files within a folder. Those differences matter when another application expects one ordinary file at a particular path.

Account and Drives

Select Google Drive when adding a Remote Server and authorize it through Google's OAuth sign-in. The connection uses the selected Google account's access to its personal drive, Shared Drives, and folders shared by other Google Drive users. Files.com folder permissions separately govern users accessing a mounted location.

The top level of the connection lists drives and shared content. It is a browsing level, rather than a writable folder. Select the actual drive or folder the workflow needs, and keep an owner for the Google authorization. Integration-Centric Profiles fit connections maintained by individual account owners; an organizational connection needs credentials and authorization your team can maintain.

Files.com renews OAuth access tokens automatically while authorization remains valid.Follow Re-authenticating Remote Servers if Google requires a new sign-in, then re-save a disabled connection after resolving the cause.

Google Workspace Files

Google Docs, Sheets, and Slides store their content in Google's document system rather than as ordinary downloadable files. Files.com exports them into Microsoft Office formats when accessed:

These exported representations are read-only through the connection. Editing an exported copy is separate from editing the original Google document. Conversion also adds processing time before the exported file becomes available.

Google Workspace Files With Sync

A Sync between two Google Drive Remote Servers transfers the exported document format. It removes the .google-apps part of the name at the destination because Google rejects uploads using that reserved name.

For example, a Google Sheet named myfile appears as myfile.google-apps.xlsx through Files.com and arrives in the destination drive as myfile.xlsx. The original Google Sheet is unchanged. The destination is an Excel file, rather than a new native Google Sheet.

Sync Destinations

For a Sync delivering files to Google Drive, select My Drive, a writable Shared Drive, or a folder within a drive, such as My Drive/Incoming. An empty destination selects the read-only connection root and is rejected when creating or editing the Sync. The connection root can still be used as a source.

A nonempty path does not establish write access. The Google account authorizing the connection must be able to upload to that drive or folder. This distinction matters when a connection can browse shared content that it may only read.

Names and Paths

Google Drive permits duplicate names in one folder and distinguishes the items by internal IDs. When Files.com resolves a path with multiple matching names, it selects the item with the most recent modification time. A path therefore does not let a workflow choose between those duplicates. Give files and folders distinct names in Google Drive when another system must reliably address a particular item.

Google Drive also permits forward slashes (/) and backslashes (\) in names. Files.com treats those characters as path separators, so items containing them are inaccessible through the connection, omitted from mounted listings, and excluded from Syncs. Rename those items in Google Drive before using them through Files.com.

Upload Delivery

With Buffered Uploads set to Automatic, Files.com receives uploads before delivering them to Google Drive in the background. Client completion then confirms receipt by Files.com, rather than remote availability. Buffered Uploads explains the delivery stage and its results. Automations can use mounted Google Drive folders as sources or destinations under the same connection and processing requirements.