Documents
Google Drive
Drive files referenced from G1 records, so evidence stays with the transaction.
Where this actually stands
PlannedPlanned
Designed and on the roadmap: we know what it would do and roughly what it takes. No code has been written, and we are not going to imply otherwise.
Connection type
API
A direct connection to the other system's interface, reading and writing on a schedule or on an event.
What it would do
Google Drive, connected.
Files linked to the transaction they support.
G1 does not ask you to replace a system that works. Where a connection exists, the point of it is to remove the person in the middle — the weekly export, the re-key, the spreadsheet that reconciles two tools that should have agreed in the first place.
Contracts, invoices and signed approvals usually live in a file store. Connecting it keeps the evidence with the record instead of in a parallel folder tree.
Every categoryModules it feeds
- DocumentsIn developmentThe paperwork attached to the record it belongs to.
- ComplianceAvailableFiling, evidence and period integrity, kept as you go.
- ContractsPlannedTerms, renewals and what they commit you to.
A connector is only as useful as the module reading it. Where the module is still in development, the connector waits for it.
Documents
Others in the same category.
- PlannedExplore
API
SharePoint
Existing document libraries, connected.
- PlannedExplore
API
Dropbox
Supporting documents where you already keep them.
- PlannedExplore
Webhook
DocuSign
Signed contracts attached to the contract record.
Names listed here are trademarks of their respective owners and appear only to describe compatibility and connection plans. No partnership, endorsement or affiliation is implied, and no third-party logos are used anywhere on this site.
Connect what you already use
Tell us how Google Drive is used where you are.
What matters is not the connector — it is the work it removes. Describe the manual step and we will tell you whether a connection actually fixes it.