Automations

File Rate Confirmations, BOLs and PODs Under the Load They Belong To

The rate confirmation comes from the broker on Monday, the signed bill of lading is a photo your driver sends on Wednesday, and the proof of delivery arrives as a scan from the receiver on Friday. All three belong to load 7842 and all three are called something else.

The short answer

Freight paperwork organizes by load, because the load is the unit you get paid on. The load number is printed on every document in the packet, so a workflow can use the Read Details from File step to pull it off each one, the Rename step to name the file by date and document type, and the Move step to file it under that load. The Email Attachment trigger picks up what brokers and receivers send, and the File Uploaded trigger covers the photos drivers send from the road, which is where most proofs of delivery actually come from.

Steps this uses

Email AttachmentFile UploadedRead Details from FileCheck File DetailsAsk AI About the FileSave a CopyRenameMove

Before and after

What actually changes

As they arrive

  • RC 7842.pdf
  • IMG_2291.jpg
  • scan0031.pdf
  • Screenshot 2026-07-17 at 4.02.11 PM.png

After the workflow

  • Loads/L-7842 Midwest Foods/2026-07-13-rate-confirmation.pdf
  • Loads/L-7842 Midwest Foods/2026-07-15-bill-of-lading-signed.jpg
  • Loads/L-7842 Midwest Foods/2026-07-17-proof-of-delivery.pdf
  • Loads/L-7851 Cardinal/2026-07-17-lumper-receipt.png

Four documents from three people, filed under the loads printed on them rather than under the day they happened to arrive.

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 rate confirmation, bill of lading or proof of delivery arrives by email or upload, read the load number and the document type off it, rename it by date and type, and file it under that load.

01

Load number first, everything else second

One folder per load, named by load number and customer. Filing by broker or by month scatters a single invoice packet across three places, and the packet is the thing you actually have to assemble.

02

Read the number off the page

The Read Details from File step takes the load number, the date and the document type off the document itself. That is what makes it work on a file the driver called IMG_2291.jpg.

03

Catch the phone photos

Most proofs of delivery arrive as a photo taken in a parking lot. The File Uploaded trigger covers those and the Email Attachment trigger covers what brokers and receivers send. Most carriers need both.

04

Send the unreadable ones to review

A bill of lading photographed at an angle in bad light sometimes has no readable load number. The Ask AI About the File step routes those to a review folder rather than guessing a load and burying the document under the wrong one.

Why the load number beats the date

Invoicing is per load. To bill, you need the rate confirmation, the signed bill of lading and the proof of delivery in one place, plus any lumper receipt or scale ticket that goes with them. Filing by date puts Monday rate confirmations a long way from Friday proofs of delivery, and whoever assembles the invoice has to go and find each one. A folder per load means the packet gathers itself as the documents arrive.

Photos are the normal case, not the exception

Drivers do not scan. They photograph a signed bill of lading on a steering wheel and send it from a parking lot, and the file is called IMG_2291.jpg and is rotated ninety degrees. Reading the load number off the image is the only approach that survives that, because there is nothing in the filename to route on and nothing useful in the folder it landed in either.

What it does not do

It files documents under the load they belong to. It does not tell you a packet is complete, because nothing in a workflow compares a folder against a list of what should be in it. It does not invoice, submit to a factoring company, or track detention. It is the filing underneath those jobs rather than the jobs themselves.

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, 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 trucking paperwork be organized?

By load, with one folder per load number and the customer name in the folder title. Every document in an invoice packet carries the load number, so that is the one key they all share. Name each file date-first with the document type, so the folder shows the sequence of a load at a glance.

Can a driver photo of a bill of lading be filed automatically?

Yes, and it is the common case rather than the edge case. The load number is printed on the bill of lading itself, so it can be read off the photo and used to file the image under the right load. A photo taken at a bad angle or in poor light may not be readable, and those go to a review folder instead of a guessed one.

Does this replace a TMS?

No. A transportation management system dispatches loads, tracks them and bills them. This handles the documents, including everything that arrives by email or as a driver photo and never gets uploaded to the system at all. Smaller carriers often run the paperwork entirely out of an inbox and a shared drive, which is where this fits.

What about assembling the invoice packet itself?

The documents land in one folder per load as they arrive, so the packet is together when you go to build it. Combining the pages into a single file is a separate merge workflow, and it is worth setting up once the filing underneath it is reliable.

The packet builds itself.

Every document under its load number the moment it arrives, from the broker or from the cab.

Build this workflow

5 GB free · No credit card required