EPAutomation systems
← All systems

Demonstration build

AI Drive File Classification & Sorting

A Google Drive workflow that detects a new file, reads its contents, classifies the document, finds the matching destination, and moves the file into the appropriate folder.

Document operations
Workflow evidenceDemonstration build / not deployed
n8n demonstration showing Google Drive file intake, document analysis, Gemini classification, folder search, and automatic file movement
The source canvas is shown as technical evidence. Browser chrome and account URLs are excluded while the n8n editor remains visible.
01 / Challenge

Where the manual work enters

Shared drives become difficult to use when incoming documents rely on people to inspect, name, and file them consistently. Misfiled records also make later retrieval slower and less reliable.

02 / System

How the workflow responds

A Google Drive trigger starts the workflow when a file is created. The file is downloaded and filtered, its document content is analysed, Gemini classifies it, and Drive search resolves the destination folder before the move step runs.

03 / Functional result

What the demonstration proves

Each accepted file reaches a classification decision and a corresponding Drive folder-move step without requiring a person to inspect and sort it first.

Signal path

One record, four controlled stages.

  1. 01

    Detect

    Watch Google Drive for a newly created file.

  2. 02

    Read

    Download, filter, and analyse the document contents.

  3. 03

    Classify

    Use Gemini to determine the appropriate file category.

  4. 04

    File

    Find the matching folder and move the document into place.

Tools in the system

  • n8n
  • Google Drive
  • Google Gemini
  • Document analysis
  • Folder routing

Demonstrated capabilities

  • Event-driven file intake
  • Document content analysis
  • AI-assisted classification
  • Automated Drive folder routing
Claim boundary

This project is a portfolio demonstration. It is not presented as a client deployment and makes no claim about production use, revenue, time saved, or business performance.

Next system

Messenger commerce agent Discuss a process like this ↗