Save and File the Documents People Drop in Slack
Somebody posted the signed contract in #clients about four months ago. You know it exists, you know roughly who posted it, and you are scrolling.
The short answer
A file shared in Slack has no home. It lives inside the message that carried it, which is why finding it later means remembering a channel and roughly a week, and why it leaves with the channel when the channel is archived. The Messaging trigger picks up files as they are shared in a connected Slack channel, the Save a Copy step gives each one a home in your drive, and the Read Details from File, Rename and Move steps name it from what is inside it and file it where it belongs. The conversation stays in Slack; the document stops being trapped in it.
Steps this uses
Before and after
What actually changes
As they arrive
- Screen Shot 2026-08-14 at 11.42.03.png
- contract_v3_FINAL.pdf
- Untitled document.docx
- IMG_2291.HEIC
After the workflow
- Clients/Acme/2026-08-14-brief-acme.pdf
- Clients/Acme/2026-08-19-contract-acme-signed.pdf
- Clients/Northwind/2026-08-21-scope-northwind.docx
- Clients/Northwind/2026-08-22-receipt-northwind.pdf
Four files posted in two channels over a fortnight, filed under the client each one names rather than the channel it was dropped in.
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 someone shares a file in a Slack channel, save a copy to my drive, read what the document is and which client it concerns off it, rename it date-first, and file it under that client.
Connect the channels that carry documents
Not every channel does. The ones worth watching are where clients, contractors and colleagues post things you will need again — #clients, #accounts, a shared channel with an agency. A channel of screenshots and memes is noise, and connecting it only makes the drive look like the channel.
Give the file a home first
The Save a Copy step is what turns a message attachment into a document. Until something does that, there is nothing to rename or move, because a file inside a Slack message has no location in the sense the rest of your tools mean it.
Let the document say what it is
The Read Details from File step reads the contract, invoice or brief itself rather than the message around it. That matters here more than in email: a Slack post is frequently just the file with "here you go" above it, so the message carries nothing to file on.
Post back where it went
The Send a Message step can reply in the channel with the folder it landed in. This is the part people notice, because it answers the question the thread would otherwise ask three weeks later.
Why Slack search does not solve this
Slack search is very good at finding messages and much weaker at finding documents, because what it indexes best is the text people typed around the file. A contract posted with "here you go" is findable by remembering who said "here you go". That is a search over the conversation, not over the documents, and it degrades exactly as the channel gets busier — which is to say, as the archive gets more valuable.
The file leaves when the channel does
Channels get archived, people leave, and shared channels with an agency or a client end when the engagement does. A document that exists only inside one of those goes with it, and nobody notices until they need it. Copying it out on arrival is the cheapest possible insurance, and it costs nothing at the moment it happens — the expensive version is reconstructing a project archive from other people's memories.
What it does not do
It copies files out of channels you connect and files them. It does not archive the conversation, preserve threads, capture messages without attachments, or act as a compliance archive for Slack — retention and export of the messages themselves are Slack's own features and a workspace setting. This is about the documents, which are the part that has to outlive the channel.
FAQ
Common questions
How do I automatically save files shared in Slack?
Connect the channels that carry documents and let a workflow copy each file out as it is posted. The Save a Copy step gives it a home in your drive, and the Rename and Move steps name it from what is inside it and file it. Nothing is downloaded by hand and the file stays in Slack as well.
Does this move files out of Slack?
No. It copies them. The message and its attachment stay exactly where they are, so links people have shared keep working and the thread still reads the way it did. What changes is that the document also exists somewhere it can be found without remembering a channel.
Can it tell which client a Slack file belongs to?
Usually, because the document says so — a contract names its parties, an invoice names its vendor. That is more reliable than filing by channel, since a shared channel often carries documents for several matters. Anything it cannot place confidently goes to a review folder rather than being filed to a guess.
What happens to files posted in DMs rather than channels?
A workflow watches the channels you connect. Direct messages are a different surface and are deliberately not part of it — a filing system that quietly copies people's private messages into a shared drive is a problem, not a feature.
The contract in #clients, in the client folder.
Connect a channel and every document posted in it gets a home, a name and a folder as it arrives.
5 GB free · No credit card required