Buzz automations can now remove a specific attachment from an action card or from a comment. This helps teams keep action records accurate when an attached file is replaced, no longer relevant, or removed from the source process.
What changed
Buzz, Buzz snippets, and compatible automation paths can use the attachment removal capability to detach one file at a time. This is intended for automated or assisted workflows, not as a new attachment menu in the Hive interface.
How to use it
Identify the action and the specific attachment your workflow needs to remove.
Configure a Buzz automation or snippet to remove that attachment when its source condition changes.
Run or test the automation, then confirm the action or comment no longer shows the file.
Repeat the removal for each additional file that should be detached.
Permissions and limitations
The person or automation running the removal needs access to the action. For comment attachments, removal follows the existing comment rules: the comment author can remove their own files, while project owners and workspace admins can remove files when their access allows it. This capability removes one attachment per operation and does not add a new manual UI control.