Save the invoice PDF to Google Drive
Well uploads the invoice PDF into your connected Google Drive folder via the file-storage API so the source document is archived alongside your other files.
Index Google Drive extracted invoice PDF, and shared drive as workspace entities, searchable in conversation and queryable from agents.
Well writes reconciled extracted invoice PDF, shared drive back to Google Drive after they clear your review queue, with the source-record link preserved. Use Google Drive as the destination for entries enriched across your other connected tools.
| From Google Drive | In Well | Relation | |
|---|---|---|---|
| Extracted invoice PDF | File in Drive folder | Uploads as | |
| Shared drive | Delivery target | Writes into |
Well uploads the invoice PDF into your connected Google Drive folder via the file-storage API so the source document is archived alongside your other files.
Connect Google Drive over OAuth 2.0: you approve on Google Drive's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.
Well brings extracted invoice PDF, and shared drive in from Google Drive on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.
Well resolves each Google Drive entity into file in Drive folder, and delivery target, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Your data from Google Drive lands as file in Drive folder, and delivery target you can search, chart, and automate, and approved records flow back to Google Drive once they clear your review queue.
Ask in plain language. Well answers from your connected Google Drive connection, resolved against the rest of your stack.
Ask anything about your Google Drive connection
Ask about your Google Drive connection…
Choose Google Drive in Well's Connections panel and authorise the folder, personal or a Workspace shared drive, where processed documents should be written. Well connects through the file-storage connector and you approve the access on Google's screen; the connector handles the upload to Drive.
When Well captures and extracts an invoice or receipt, it uploads the PDF to the connected Drive folder, filing the finished document where your team already works, including a Workspace shared drive.
Your team opens and shares the uploaded files through Drive's own permissions. Because this is file storage rather than accounting, Well files documents into the folder instead of recording entries anywhere, and importing files from Drive back into the workspace is on the roadmap.
Authorisation takes about a minute. Processed files are written into Drive as they clear extraction; Drive-to-Well import is not live yet.
Google Drive connects through Well's file-storage connector, which authorises the Drive folder or shared drive Well may write to and uploads extracted PDFs there for you. The capability is outbound today: Well files a processed document into Drive and does not read files back, since inbound import is still coming soon. The grant lets Well deposit documents into your storage, not post entries to an accounting ledger.
Read Google Drive records
Endpoints the Google Drive API token grants, scoped by your consent.
Resolve extracted invoice PDF, and shared drive across your stack
Match identifiers in Google Drive against the same entities your other connected tools expose, so each record carries cross-tool context.
Deliver documents to your Google Drive inbox
Well forwards approved documents to your Google Drive email-in address; Google Drive drafts the record and you post it. No write credential to Google Drive is requested.
Store Google Drive passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
The connection lets Well deposit processed documents into your Google Drive folder. After Well extracts an invoice or receipt, it uploads the PDF to the Drive folder you connected, so the finished document is filed where your team already keeps things. The flow runs outbound: documents go from Well into Drive, not the other way around yet.
Reading from Drive is not live; it is marked coming soon. So Well does not scan or import your Drive folders into the workspace today. What works now is the outbound side, uploading extracted PDFs into Drive. The page is written around that live behaviour, with Drive-to-Well import noted as a roadmap step rather than a current feature.
Yes. Well can write to a Google Workspace shared drive just as it can to a personal Drive folder, so the processed PDFs land in the team space everyone already opens. Whoever has access to that shared drive sees the uploaded documents through Drive's normal permissions. Well is adding files to the drive, and Drive governs who can read them.
No. This is a file-storage connection, so Well's action is uploading a document to a Drive folder, not recording a bill or an accounting entry. Your accounting tools remain where entries live. Drive is where the processed PDF is stored and shared; expecting it to keep your books would misstate what the connector is for.
Once a document clears extraction, Well uploads the PDF to the connected Drive folder in the background, so it shows up in Drive shortly after. Well writes the file and Drive holds it; there is no inbound sync pulling Drive changes back today. The folder gains the finished document and your team can take it from there.
Disconnecting Drive in Well ends the upload access at once, so Well stops writing new files into your folder. Everything Well already uploaded remains in Google Drive under your team's permissions, untouched by the disconnect. Removing the connection stops future writes; it does not reach into Drive to delete what is already there.
More in Cloud storage
Popular cross-category
Connect once. Every extracted invoice PDF, shared drive from Google Drive becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.