What does AIDA's Google Drive integration do beyond OCR?

AIDA's Google Drive integration transforms Drive into a self-organizing archive: AIDA reads every document, extracts the data you need, and saves it to Google Drive with a clear name and in the right folder. For those who work daily with Gmail and Google Workspace, this means going from attachment to archive without manually opening, renaming, or moving files.

Google Drive is one of AIDA's native integrations, alongside Microsoft SharePoint and OneDrive, Dropbox, SAP, and Xerox devices. In this article, we look at what AIDA adds to the features Google already offers, how to configure the integration, and which documents are best suited for this kind of archiving. If your archive is in a Microsoft environment, read our article on SharePoint and OneDrive integrations with AIDA; if you use Dropbox, check out the one on Dropbox integration with AIDA.

What is AIDA's Google Drive integration?

It is a destination within AIDA: the endpoint for documents after processing. Files enter AIDA via email, smartphone, scanner, or web upload, are analyzed, and then saved to your Google Drive with a name and path determined by their content.

The engine behind this analysis is Intelligent Document Processing (IDP): a technology that recognizes text using OCR, even when handwritten, understands what type of document it is, and extracts individual data fields such as customer name, number, date, or amount.

Google Drive already reads PDFs: why do you need AIDA?

Because reading text is not enough for archiving. Google Drive can convert a PDF or photo into a Google document with recognized text, but the result is a new text file: no data is extracted, the file is not renamed, and nothing moves it to the correct folder.

According to the official Google Drive guide, conversion accepts files up to 2 MB and typically does not recognize tables, lists, or columns — precisely the elements that matter most in invoices, purchase orders, and delivery documents.

AIDA goes one step further. Rather than simply transcribing the document, it identifies the fields you have configured, validates them, and uses them to determine the file name and storage location. It handles documents up to 2,500 pages and 100 MB, across dozens of different formats, including digitally signed P7M files.

How do you configure the Google Drive integration?

It is configured entirely within the AIDA interface, with no coding required. The process is always the same: you teach AIDA the document type, choose where it comes from, and decide where and how to archive it in Drive.

1. Create a document type and specify the data to extract. All you need is one example: select the field, click on the value in the document, and AIDA learns to extract it from subsequent documents as well, without lengthy training cycles.
2. Choose your input sources: the dedicated email address AIDA creates for each document type, the AIDA Mobile app, WhatsApp, web upload, Xerox ConnectKey scanners, electronic invoices from the Exchange System (SDI), or Zapier.
3. Connect Google Drive using the "Connect a Google Drive account" button, or reuse a connection already created for another document type.
4. Select the folder and archiving rules: the destination folder in Drive and, on the Data-driven page, which data to use for the file name and subfolders.
5. Decide how to handle duplicates: overwrite the existing file or keep both, adding a sequential number to the new one.

The connection uses the OAuth 2.0 protocol: you authorize AIDA directly from your Google account, without sharing your password. You can find details on data protection and certifications on the AIDA security and certifications page.

How does a document travel from email to Google Drive?

A typical case is a delivery note (DDT) sent by a supplier via email. The DDT arrives at AIDA's dedicated inbox as an attachment, and AIDA extracts the configured data fields:

With the destination folder set to Delivery Notes, a subfolder per supplier, and a file name composed of the supplier name and number, the DDT is saved in Google Drive as follows:

Delivery Notes/Bianchi Spa/Bianchi Spa - DDT 1245_A.pdf

The slash in number 1245/A has been replaced with an underscore: AIDA automatically substitutes characters that Google Drive does not accept in file and folder names. The next DDT from the same supplier lands in the same folder, following the same naming pattern, making it easy to find in Drive right away.

AIDA, Google Drive OCR, or Google Document AI: what are the differences?

These are three tools with different purposes: Drive's OCR makes text readable, Google Document AI is a Google Cloud service that developers use to build their own applications, and AIDA is a ready-to-use platform that extracts data and archives documents without any programming.

With Document AI, processing a document requires a Google Cloud project, active billing, an enabled API, and credentials, as outlined in the Google documentation; archiving the results in Drive with custom names and folders then requires building a dedicated integration. With AIDA, the same outcome — documents read and archived — is ready out of the box and managed by the team that works with those documents every day, with no development projects needed.

Which documents are best suited for archiving on Google Drive with AIDA?

Any recurring documents that someone currently opens, reads, and renames before saving. Here are the most common use cases:

• Logistics: delivery notes (DDT), CMRs, and proof-of-delivery documents archived by supplier, customer, or shipment. Learn more in the article on AIDA in the transport and logistics sector.
• Purchasing and administration: purchase orders, order confirmations, and electronic invoices received from the SDI, including P7M-signed files. For matching ordered, delivered, and invoiced quantities, there is AIDA Match.
• Healthcare: reports, forms, and administrative documentation, as described in our article on workflows in the healthcare sector.
• Energy and utilities: supply contracts, bills, and customer files, as illustrated in the article on innovation in energy supply services.

Alongside Google Drive, you can also use AIDA's document archive, which links related documents and maintains a full history for every file.

Frequently asked questions about the Google Drive integration

Do you need a developer to connect AIDA to Google Drive?

No. You connect your Google account, choose a folder, and set the archiving rules directly from the AIDA interface. The Google Drive integration is designed to be managed by the people who use those documents every day.

Can AIDA process documents already stored in Google Drive?

Yes, via Zapier. Enable the Zapier input in the document type and create a Zap with the trigger "Google Drive → New File in Folder" and the action "AIDA → Upload Document": every file added to the folder is processed by AIDA and can be returned to Drive, already renamed, in a different folder.

Can I archive attachments I receive in Gmail to Drive?

Yes. You can forward emails to the document type's dedicated inbox, or use Zapier with the trigger "Gmail → New Attachment". AIDA can also convert the email body text into a PDF document, which is useful when the information is in the message itself rather than in an attachment.

What happens if a file with the same name already exists in Drive?

You decide: AIDA can overwrite the existing file or keep both, adding a sequential index to the new one (for example file.1.pdf) or the letter "z" followed by the index (file.z1.pdf).

Which AIDA plan includes the Google Drive integration?

Destinations are included from the Personal plan, which allows one; from the Professional plan onwards they are unlimited, so you can use Google Drive alongside Dropbox, OneDrive, or SharePoint. Full details are available on the AIDA pricing page.

Try AIDA's Google Drive integration

If your team lives in Google Workspace, AIDA can deliver documents to Drive already read, renamed, and archived — no development projects required. Explore all AIDA integrations or book a personalized demo to see it in action with your own documents.