Blog · 22 October 2026 · 6 min read
Local AI with Gmail and Google Drive: what it reads and what it doesn't do
Anyone who works with Google Workspace already has a good part of the company's memory there: years of emails and folders of documents. The question always comes before the signature: can the local AI use them? And above all, can it cause trouble, for example by replying to a customer in my place?
In short: yes, a local AI connects to Gmail and Google Drive, and it does so in read-only mode. A sync program downloads new messages and documents to the company's computer at scheduled intervals and adds them to the archive in which the AI looks for answers. The AI does not change or delete anything on Drive and does not send emails by itself: if you ask it for a reply, it prepares a draft that you reread and send yourself.
What does it do on its own and what needs your involvement?
After the initial configuration you do not have to do anything: email and documents are read automatically. For each connection it is worth getting answers to four questions, always the same ones:
| Question | Gmail | Google Drive |
|---|---|---|
| What is automatic? | Reading new messages | Synchronisation of the documents in the chosen folders |
| What do I need to do? | Nothing | Nothing: you save the files where you already save them |
| How often does it update? | At scheduled intervals | At scheduled intervals |
| Does it only read or does it act? | It reads. On request it prepares a draft in the chat | Read-only |
For this job there is an official Open WebUI tool, oikb, created to keep the document archive in sync with external sources: its connectors include the computer's folders, Google Drive and Gmail. On each pass it compares what it finds with what it has already loaded, adds only new or modified files and removes those that no longer exist.
How often are email and documents updated?
At intervals decided at installation: not in real time. Syncing with Google's services runs in the background and can be scheduled in two ways: every so many minutes or hours (for example every 30 minutes), or at set times (for example on weekdays at 6 in the morning).
In practice this means that an email that arrived two minutes ago may not be in the archive yet. For typical work (finding an agreement, reconstructing a customer's history, summarising a long exchange) this is not a limitation. If, on the other hand, you need a message that has just arrived, you paste it into the chat.
Tip: a shorter interval doesn't make the AI any smarter, it just keeps it more up to date. An update every hour for documents and a more frequent one for email is usually enough.
Can the AI send emails on my behalf?
No, and it is best that it stays that way. Google distinguishes between the permissions a program can request on a mailbox: there is a read-only permission ("view messages and settings") separate from the one that allows drafts to be managed and messages sent. The connection is set up with the former: something that reads cannot send.
When you ask "reply to this request for a quote", the AI writes the draft in the chat, starting from the exchange it has read and from your documents. You re-read it, correct it and send it from your email program. It is one extra step, but it is the one that prevents the wrong reply going out to a customer without anyone having seen it.
The same rule applies on Drive: read-only permission allows files to be viewed and downloaded, not changed. The AI does not rename, move or delete anything in your folders.
Does my data leave the company?
No: the route is one-way, from Google to your computer. Emails and documents stay where they are today, that is, on Google's servers, and in addition a copy arrives on the company's machine, where they are read and indexed. The questions you ask, the answers and the search index stay on site.
The difference from a cloud assistant is this: your documents are not sent to a third-party service to be processed. It is the principle we explain in the guide on how to connect a local AI to your company documents.
One thing to decide beforehand: which mailbox and which folders. Everything that goes into the archive can appear in the answers of anyone with access to that archive. Management or HR email does not go in the same container as the price lists.
What it does not do well
- Real time. The archive is up to date as of the last sync, not to the second.
- Actions. Archiving messages, applying labels, creating folders or saving the draft directly inside Gmail requires write permissions. It can be done, but it is a decision to be taken separately and with caution: for Google, the permission that manages drafts is the same one that allows sending.
- Difficult attachments. Crooked scans, photos of documents and very large spreadsheets are read less well than a clean PDF.
- Shared mailboxes and several people's accounts. Each mailbox has to be connected and authorised: connecting one is not enough to read them all.
- Changes decided by Google. If Google changes the permissions or the way access works, the connection has to be adapted.
How we set it up
During the site survey, on site at the client's premises and throughout Italy, we choose together which mailboxes and folders to connect and who will be able to query them. We then configure the connection as read-only, with the credentials registered to the company, and set how often it updates. In the training we show how to ask for a draft and how to check which message the AI took a piece of information from.
Once installation is finished, the system is yours and works without us. You will find the rest of the project on the Local AI for businesses page; if you want to understand what can be connected in your case, write to us.
Sources
- Open WebUI – Knowledge Base Sync (oikb): sources, connectors and incremental sync
- Open WebUI – oikb daemon: interval and scheduled syncs
- Open WebUI – Knowledge (knowledge bases)
- Open WebUI – RAG: document search and citations
- Google – Gmail API: list of permissions (scopes)
- Google – Drive API: list of permissions (scopes)
About the author: Dabryx
Dabryx is an Italian software house that installs local AI in companies, on site across Italy, on servers or Macs. The basic installation starts at €2,900, hardware not included, and consulting at €100 per hour. The office is in Rocca Priora, near Rome.
We also install local AI in Rome, Milan, Parma and Reggio Emilia, and we develop custom management systems and custom software.
Frequently asked questions
Can a local AI read Gmail emails?
Yes. A synchronisation program downloads the messages onto the company's computer at scheduled intervals and adds them to the archive in which the AI looks for answers. The connection is set up with a read-only permission.
Can the local AI send emails by itself?
No. With read-only permission it cannot send anything. On request it prepares a draft in the chat, which you re-read and send yourself from your email program.
Can the AI change or delete files on Google Drive?
No. The connection to Drive is read-only: the AI sees and downloads the documents in the chosen folders, but does not change, move or delete them.
How often does the AI see new emails and documents?
At the frequency decided at installation, for example every 30 minutes or every hour. It is not a real-time connection: a message that has just arrived enters the archive at the next sync.
Want an estimate for your company?
Tell us how many people will use the AI and what for: we'll tell you which configuration you need.
Response times
Within 2 hours on business days (9:00–18:00) for clients with a support contract.
AI consulting
Basic installation from €2,900, consultancy from €100 per hour, on your company's server or Mac.
Where we work
Throughout Italy: we come on site to the client's premises and also support you remotely.