Google Drive integration

Ideas & Features
1

Google Drive integration, to have a field that can attach directly a doc or sheet from a connected Google Drive account, either personal or Google Workspace shared account. This is what for example is possible with Clickup. Will make many users happy.

1 Like
2

The idea here specifically, is to allow private google drive items (like unplublished or unshared docs) to be accessible also.

Embedding private Google Drive items like Docs into third-party platforms like fibery while ensuring that only authorized users can access them involves a combination of Google Drive’s sharing settings and the third-party platform’s embedding capabilities. Here’s a step-by-step guide on how fibery could potentially make this possible:

  1. Google Drive API Integration:
  • Fibery would need to integrate with the Google Drive API. This allows the platform to request access to a user’s Google Drive files.
  • When a user wants to embed a private Google Doc, they would be prompted to grant fibery permission to access their Google Drive.
  1. OAuth 2.0 Authentication:
  • The Google Drive API uses OAuth 2.0 for authentication and authorization. When a user tries to embed a private Google Doc, they would be redirected to a Google login page.
  • After logging in, they would grant fibery the necessary permissions to view (or edit) the specific Google Doc.
  • Google would then provide fibery with an access token, which the platform can use to access the Google Doc on behalf of the user.
  1. Embedding the Document:
  • Once fibery has the necessary permissions, it can use the Google Drive API to retrieve the content of the Google Doc and display it within an embedded frame or widget in fibery.
  • This embedded frame would only display the content to users who have granted fibery access to the Google Doc.
  1. Access Control:
  • Fibery would need to implement access control mechanisms to ensure that only authorized users can view the embedded Google Doc.
  • For instance, if a Google Doc is shared with specific email addresses, fibery could check if the logged-in user’s email matches one of the authorized addresses before displaying the content.
  1. Refreshing Access Tokens:
  • OAuth 2.0 access tokens are temporary and expire after a certain period. Fibery would need to handle token expiration by either:
    • Silently refreshing the token using a refresh token (if Google provides one).
    • Prompting the user to re-authenticate when the token expires.
  1. Revoke Access:
  • Users should have the option to revoke fibery’s access to their Google Drive at any time. This can be done through Google’s account settings, but fibery should also provide a clear option within their platform.
  1. Security Considerations:
  • All interactions between fibery and Google Drive should be encrypted using HTTPS to ensure data privacy.
  • Fibery should store access tokens securely and ensure that they are not exposed to unauthorized parties.
  1. User Experience:
  • The embedding process should be as seamless as possible for users. Clear instructions and prompts can guide users through the authentication and embedding process.
  • Users should be informed about the permissions they are granting and have the ability to manage or revoke these permissions.

By following these steps and ensuring robust security and privacy measures, fibery can provide users with the ability to embed private Google Drive items while maintaining access controls and permissions.

4 Likes
3

I use Google Drive as the primary cloud storage solution for my business. I’d like to second this feature request but with a note that native integrations into the existing Files field would be ideal for me. ClickUp is a good reference here (although their gDrive integration times out too frequently)
A separate field per storage app would create friction and potentially confusion in the UI when collaborating. Allowing items in the files field to come from a 3rd party storage app would keep databases clean and preserve good asset management practices.

As it is now, we can’t embed private google drive assets into rich text fields. In the short term, this milestone would be greatly appreciated.