Keep Client Feedback With the Asset It Refers To
Three months later the client says they never approved that headline. The approval exists — in a Slack thread, in a channel that has since been archived, from an account manager who has left.
The short answer
Feedback is only meaningful attached to the version it was about, and it almost always arrives somewhere other than where the file lives: a Slack message, an email reply, a marked-up PDF. A workflow uses the Messaging and Email Attachment triggers to capture it, the Read Details from File step to identify the client and campaign it concerns, and the Move step to file it into that campaign alongside the version it refers to. The Save a Copy step matters here, because an attachment in a thread has no existence outside it.
Steps this uses
Before and after
What actually changes
As they arrive
- Slack thread
- Re: Re: banner feedback.eml
- markup.pdf
- approved!!.png
After the workflow
- Acme Corp/Spring 2026/Review/2026-03-05-feedback-round-1.pdf
- Acme Corp/Spring 2026/Review/2026-03-07-markup-headline.pdf
- Acme Corp/Spring 2026/Review/2026-03-09-approval-email.pdf
- Acme Corp/Spring 2026/Approved/2026-03-09-banner-hero.png
Feedback and the approval that followed it, filed next to the version each one was about.
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 feedback arrives in Slack or by email, save a copy, read which client, campaign and asset it refers to, rename it by date and round, and file it into that campaign beside the version it is about.
Capture from where it actually arrives
Slack, Teams and email, not a portal you wish clients used. The Messaging and Email Attachment triggers cover the routes feedback really takes, which is the only way this works.
Name feedback by date and round
The Rename step writes both, so a campaign folder shows the sequence: v1 sent, round one comments, v2 sent, approved. That sequence is the record of how a decision was reached.
File it beside the version, not in a Feedback folder
A general feedback folder loses the connection between a comment and what it was about. The Move step puts it in the campaign next to the asset, which is where it means something.
Save the attachment, not the link
A file that exists only as a Slack attachment disappears with the workspace, the retention policy or the channel. The Save a Copy step gives it an independent home.
An approval in a chat thread is not a record
Chat is designed to be ephemeral and is often configured that way — retention policies delete, channels get archived, workspaces get migrated, people leave and their DMs go with them. An approval that exists only as a message is an approval you will probably still have and cannot rely on having. Saving it as a file next to the asset converts a conversation into a record, which is a different kind of thing.
Feedback without its version is noise
"Make the headline bigger" means nothing six weeks later unless you can see which headline. Filing comments into a general feedback folder preserves the words and loses the referent, which is most of the meaning. Next to the version it concerns, the same comment is self-explanatory — and the sequence of rounds shows how the work actually got to where it ended up.
What it does not do
It captures and files. It does not consolidate three people's comments, resolve contradictory feedback, track which revisions were actually made, or constitute a legal record of agreement. It makes the evidence available and organized. Whether an exchange amounts to approval is a judgement about your client relationship and your contract.
FAQ
Common questions
How should client feedback be organized?
Filed into the campaign next to the version it refers to, named by date and round. Feedback separated from the asset it concerns loses most of its meaning — a comment about a headline is only interpretable alongside the headline it was about.
Why save approvals out of Slack or email?
Because chat is configured to be ephemeral. Retention policies delete messages, channels are archived, workspaces get migrated, and people leave with their DMs. An approval that exists only as a message is one you will probably still have and cannot depend on having when it matters.
Should feedback go in its own folder?
No. A feedback folder keeps the words and loses what they referred to. Filing comments beside the version they concern means the sequence — draft, comments, revision, approval — reads as the history of how the work got to where it ended up.
Is a saved approval legally binding?
That is not a question a filing system answers. What it provides is an organized, dated record of what was sent and what came back. Whether a given exchange constitutes approval depends on your contract and your relationship with the client.
The approval, next to the version.
Saved as a file rather than left in a thread that may not survive.
5 GB free · No credit card required