How to Merge Documents Automatically as They Arrive

TL;DR: Merging documents by hand is fine for one file and a waste of a morning for two hundred. A workflow with a Merge Files step reads the files, orders them, and combines them into one, so a closing packet or a monthly expense bundle assembles itself as the pieces arrive. For a single merge right now, a free browser tool is faster than any automation.

Every team has a packet. The closing packet, the board pack, the month-end expense bundle, the tender submission, the onboarding file that goes to payroll. It is always the same set of documents in the same order, and it is always assembled by a person who opens a PDF editor, drags eleven files into a pane, worries about whether the inspection report goes before or after the appraisal, exports, renames, and sends.

That job is not hard. It is just repetitive, and it happens at the worst possible time, usually the afternoon of a deadline. It also fails quietly: the packet goes out with last month's cover sheet, or missing page four, and nobody notices until a counterparty does.

A document merge workflow is a standing instruction that combines files into one as they arrive, in an order you describe once, without anyone opening an editor.

Should you automate a merge at all?

If you need to combine three files once, use a tool and move on. Automation is worth building when the same merge happens repeatedly, when the order matters and gets it wrong sometimes, or when the pieces arrive over days from different people.

Our free merge PDF tool does a one-off merge in the browser with nothing to configure, and compress PDF handles the file that is too large to email afterwards. Reach for a workflow when you are doing that same merge every week, or when the pieces trickle in from a mailbox, a Slack channel, or a shared folder and somebody has to notice they are all finally there.

How document merging usually works

Most merging today happens in one of three places, and each has a real cost.

A PDF editor. Acrobat and its alternatives combine files reliably and let you see the result. Someone has to do it, every time, and the ordering lives in that person's head.

A script. A developer wires up a library to concatenate files in a folder. It works until the ordering rule needs judgment, for example when a two-page addendum has to follow the agreement it amends rather than the file that happens to be alphabetically next.

A connector platform. Zapier and Make can chain a merge action, but they decide order from filenames, dates, or the order files arrived, because that is the metadata they hold. When the filename is scan_0043.pdf, the metadata cannot tell you what the document is.

The gap in all three is the same. Ordering a packet correctly usually requires knowing what each document is, and that information is inside the documents.

How do you merge documents automatically?

A workflow in The Drive AI starts from a sentence. You type what should happen, and the steps appear on a canvas where you can edit them. The step that does the combining is Merge Files, and its field asks a plain question: "How should files be merged?" You answer in plain English, for example "combine into one PDF, ordered by date".

Merge Files carries the ai badge, which means it opens the files and reads them to work out the order. That badge is the honest part: it costs a little per file, and like any step that reads a document it can occasionally be wrong. That is why an approval step belongs in front of anything that goes to a client.

The steps that usually surround it:

Check File Details (free) gates the branch on type, age, size, name, or which folder the file is in. Use it to make sure only PDFs and documents reach the merge.
Read Details from File (ai) pulls out named values such as client, property address, or month. Later steps can use those values, so the merged file can be named from what was inside it.
Rename (ai) names the combined file.
Move (ai) files it where the packet belongs.
Ask a Person to Approve (human) pauses the workflow and shows someone the plan before the packet is filed or sent.
Send a Message (external) tells a Slack channel or an email address that the packet is ready.

Every run is recorded in an activity feed, can be replayed on the canvas exactly as it happened, and can be retried from the step that failed.

Example merge workflows

Each of these is the sentence you would type.

A month-end expense bundle:

Every month on the 1st, go through every file in Finance/Expenses/Last Month and combine them into one PDF ordered by date, named "Expenses <month> <year>", and file it in Finance/Expense Reports.

A closing packet that assembles itself as pieces arrive:

When a document arrives for a property, read the property address and the document type. File it under Transactions/<address>/Documents. Once the purchase agreement, the disclosures, the inspection report, and the title commitment are all there, combine them into one PDF in that order, named "<address> Closing Packet", and ask Maria to approve before it goes to Transactions/<address>/Final.

A board pack from a Slack channel:

When a file is shared in #board-prep, save a copy to Board/Prep. On Friday at 4pm, combine everything in Board/Prep into one PDF ordered by the agenda, name it "Board Pack <date>", file it in Board/Packs, and message #board-prep that it is ready.

A scanned batch that has to be split before it can be merged:

When a scan lands in Scans/Inbox, split it into separate documents. Read the client from each one and file it under Clients/<client>/Intake. Then combine each client's intake documents into one PDF named "<client> Intake".

That last one is worth sitting with, because it is the pattern people do not expect. Splitting and merging are the same job seen from two ends: a scanner hands you one file that should be eleven, and a process hands you eleven files that should be one. Splitting scanned documents automatically covers the other direction.

Merge options compared

Capability	PDF editor	Script	Zapier or Make	The Drive AI Workflows
One-off merge	Yes	Overkill	Overkill	Use the free tool instead
Runs without a person	No	Yes	Yes	Yes
Orders by filename or date	Manually	Yes	Yes	Yes
Orders by what each document is	A person decides	No	No	Yes, Merge Files reads the files
Names the result from document contents	Manually	No	No	Yes, with Read Details from File
Waits for the whole set to arrive	A person notices	You build it	Limited	Yes, on a schedule or a condition
Holds the packet for approval	No	No	Additional steps	Yes, the plan is shown first
Record of what was combined	No	Logs you write	Task history	Activity feed with replay and retry

What will a merge workflow not do?

The limits matter more than the features here, because a packet that is wrong is worse than a packet that is late.

The ordering is inferred, not guaranteed. Merge Files reads the documents to order them, and an ai step can occasionally be wrong. Put Ask a Person to Approve in front of anything that leaves the building.
It combines documents, it does not edit them. There is no step that adds a cover page, stamps page numbers, applies a watermark, or redacts. Those are not workflow steps.
Approvals expire. An approval waits 24 hours, 3 days, or 1 week, whichever you set, with 3 days the default. After that the file takes the Expired exit, and if nothing is connected there, nothing happens and the expiry is recorded.
Files in a connected drive stay there. A workflow watching a folder in Google Drive, OneDrive, SharePoint, or Dropbox works inside that storage. Nothing is imported unless you add a Save a Copy step, and then only to the place you name.
Connected accounts need a paid plan. Workflows on files uploaded to The Drive AI work on every plan. Connecting Gmail, Outlook, Slack, Teams, Google Drive, OneDrive, SharePoint, or Dropbox needs the Max plan on a personal workspace, or any Team plan. Each file a workflow processes counts once against a monthly allowance.

Setting up a merge workflow

Decide what the packet is. Write down the documents it contains and the order they belong in. This is the part that takes thought, and it is the part you only do once.
Choose when it should assemble. On a schedule, if the packet is periodic. On arrival, if it should build as pieces land. A scheduled source can go through new and changed files only, or every file every run.
Describe it in one sentence. Include the order, the name, and the destination. The steps appear on the canvas, each with its cost badge.
Add a person where it matters. Put Ask a Person to Approve before the packet is filed or sent, and choose whether admins, specific people, or everyone can decide.
Run it once and open the activity feed. Check the order on a real set of documents before it runs unattended. Any run can be replayed exactly as it happened.

For how these steps fit together across every source and action, see the document workflow steps guide and the complete guide to automated document workflows.

Frequently Asked Questions

Can I merge documents automatically as they arrive?

Yes. A workflow can watch a folder, a mailbox, or a channel and combine files into one as the pieces land, or on a repeating schedule. The Merge Files step reads the files to order them, so the order can follow what each document is rather than its filename. For a single merge, a browser tool is faster than setting up a workflow.

How does it decide what order to merge files in?

You describe the order in plain English, for example ordered by date or in agenda order, and the step reads the documents to apply it. That is why it can put an addendum after the agreement it amends rather than wherever the filename falls alphabetically. Because the step reads the files, it costs a little per file and can occasionally be wrong.

Can it name the merged file from what is inside the documents?

Yes. Add a Read Details from File step before the merge and name the values you want, such as client, property address, or month. Those named values become available to later steps, so the Rename step can build a filename like the client name plus the document type plus a date, without anyone typing it.

Does merging move my files out of Google Drive or SharePoint?

No. A workflow watching a folder in a connected drive works inside that storage. Files are not imported unless the workflow includes a Save a Copy step, and then only into the place you name. Email and chat attachments are the exception, because they have no storage home until a workflow gives them one.

Can a person check the packet before it goes out?

Yes. Ask a Person to Approve pauses the workflow and shows the approver the plan, not just a question. You choose whether admins, specific people, or everyone can decide, and how long it waits: 24 hours, 3 days, or 1 week. The approved, rejected, and expired outcomes each have their own path on the canvas.

What if some documents in the set have not arrived yet?

Build the workflow so the merge runs on a schedule, or behind a condition that checks the set is complete. Files arriving in the meantime are filed as they land. A scheduled source can be set to go through every file on every run, which is also how a folder that already holds a backlog gets handled rather than only new arrivals.

Start with one packet

Pick the packet your team assembles most often and describe it once. The next deadline it can build itself while someone reads it instead of dragging it together. Build your first workflow, or see how Workflows handle files from every source.