Automations

Organize Client Files When You Have a Dozen of Them

Filing one contract takes ten seconds. The problem is doing it consistently for twelve clients across three years, while the work that actually pays is always more urgent.

The short answer

Use one folder per client with the same four subfolders inside every one of them — contracts, invoices, briefs, delivered — and name every document date-first in ISO form so it sorts chronologically: 2026-08-14-invoice-acme-0231.pdf. Identical structure per client is what makes it survivable; a bespoke arrangement for each is what collapses. Then a workflow watching your drive uses the Rename step to name each document from what is on it and the Move step to put it in the right client folder, while documents arriving as Gmail, Outlook or Slack attachments get a home first through the Save a Copy step.

Steps this uses

File UploadedEmail AttachmentMessagingSave a CopyRead Details from FileRenameMove

Before and after

What actually changes

As they arrive

  • contract.pdf (email, Acme)
  • Scan_0042.pdf (Slack, Northwind)
  • invoice FINAL.pdf

After the workflow

  • Clients/Acme/contracts/2026-08-02-contract-acme.pdf
  • Clients/Northwind/briefs/2026-08-04-brief-northwind.pdf
  • Clients/Acme/invoices/2026-08-14-invoice-acme-0231.pdf

Three documents from three different places, filed under the client each belongs to.

Setting it up

Described once, then it runs

This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.

When a document arrives by email, Slack or upload, save a copy, read the client and the document type off it, rename it date-first, and file it under that client in contracts, invoices, briefs or delivered.

01

The same four folders in every client

contracts, invoices, briefs, delivered. Resist customising per client — the value is that you never have to remember which client uses which arrangement.

02

Date first, in ISO form

2026-08-14-invoice-acme-0231.pdf. ISO dates sort chronologically in an alphabetical listing, which every file browser gives you by default. The client name is already in the folder, so it is there for search rather than for sorting.

03

Catch documents where they arrive

Contracts come by email, briefs come by Slack, deliverables go out from your drive. The Email Attachment and Messaging triggers pick up the first two, and Save a Copy gives them a home — an attachment has none until something files it.

04

Let the workflow do the filing

The Rename step names each document from its own contents and the Move step files it under the right client. Cloud storage files are renamed and moved in place, so links and permissions survive.

Why identical beats bespoke

The instinct is to shape each client folder around how that client works. It is the wrong instinct at a dozen clients, because it means every filing decision requires remembering that client's arrangement first. Identical structure everywhere means the decision is the same every time, which is the property that lets a structure survive a busy month.

The folder carries the client, the filename carries the date

Repeating the client name in every filename wastes the most valuable position in the name on information the folder already gives you. Put the date there instead and the folder sorts itself chronologically. Keep the client in the filename only where files leave the folder — an invoice you email out benefits from being called invoice-acme rather than invoice.

What this is not

This is filing, not a business. It does not raise invoices, chase payment, hold a client pipeline or send proposals — that is what a CRM like HoneyBook or Dubsado is for, and if what you actually need is the whole back office then a filing layer will disappoint you. What it does is make sure that when a client asks for the signed version from March, you have it in one place with a name that says what it is.

Limits

What to know before you build it

It runs on new files, not your backlog

This workflow fires when a file arrives. It will not go back over the documents already sitting in the folder, so switching it on leaves the existing pile exactly where it is. Working through what is already there is a scheduled run instead, which is a different workflow.

Organize the files you already have

It needs a connected account

This workflow reads files out of an email inbox and a chat workspace, so it cannot run until that account is connected. Connecting one is on the Max plan, or on any team workspace. There is no version of this particular workflow that runs on the free plan, because the files it organizes never arrive in The Drive AI on their own.

FAQ

Common questions

How should a freelancer organize client files?

One folder per client, with the same four subfolders inside each — contracts, invoices, briefs, delivered — and every document named date-first in ISO form so it sorts chronologically. Keeping the structure identical across clients is what makes it survivable.

Should the client name go in the filename or the folder?

The folder. Repeating it in the filename spends the most useful position on something the folder already tells you. Put the date there instead. Add the client name only for files that leave the folder, like an invoice you email.

How do contracts from email end up in the right client folder?

The Email Attachment trigger picks them up, the Save a Copy step gives them a home since an attachment has none, and the Rename and Move steps name the document from its contents and file it under the client it belongs to.

Is this a replacement for a CRM?

No. It files documents. It does not raise invoices, chase payment, or manage a client pipeline. If you need the whole back office, a CRM is the right tool and this sits alongside it.

Twelve clients, one filing decision.

Made once, applied to every document that arrives.

Build this workflow

5 GB free · No credit card required