Project Backup

Automatically copy matching files between Mac folders

Use this Rule for project exports or deliveries that need a second local copy. It copies rather than moves the matching item, so the original remains available in the source folder.

When: An item is added or renamed in ~/Downloads. If: The event’s filename contains Project. Do: Copy File to ~/Documents/Project Backups, using a numbered name if the destination name already exists. The two Triggers feed the same matching and copy path.

Configure and try it

1. Import with Open this Rule in Rulr and set the watched folder in both the added and renamed Triggers.
2. Replace Project with the filename text that identifies the files you want to copy.
3. Select an existing writable backup folder outside the watched source and review the name-conflict policy.
4. Enable the Rule and add a disposable matching file. Confirm the original remains and the copy appears. Rename a test item to a matching name, then try a nonmatching name to check both event paths and the filter.

Requirements and limits

Folder Contents Changed requires Rulr Pro; Copy File itself is available without Pro. Rulr needs access to both folders.

This is an event-driven extra copy, with no explicit wait for a file still being written. It is not a full backup system: there is no version retention, deletion propagation, existing-folder scan, or monitoring of later content edits. Repeated matching events can create additional numbered copies. For triggering your own processing instead, see Run Shortcut for Folder.

Does this keep two folders in sync?

It makes an extra copy when a matching item arrives or is renamed. Editing the original later does not update the copy, and deleting the original does not delete its copy. Use the Rule for incoming project deliveries that need a second copy, rather than continuous folder synchronization.