renaming source file after copy to new folder

Hi
I am trying Hazel out before purchase anything and so far I like it, but I have a specific task I would like to do.

Background:
I am mixing and mastering music a lot and to referens-listening results I am using an app called CloudBeat. Inside that app I can build playlists etc, it's great, and I can pick the songs up directly from the cloud and play them from there. I don't need to physically add the songs on the device. The problem is that it works really bad with iCloud. It works, but not as smoothly as other apps as dropbox etc. (I have left dropbox, so go back is not an alternative at the moment).
Now, all my bounces and mixes and masters will be saved on different places on my Icloud Drive every time I working an a new project, as I never know what the projects will be, and I am using Protools default bounce-folders always, that makes things clear to me and I like it.

What I am trying to do with Hazel:
Copy all files (audio) inside my "PROTOOLS"-folder which have "_bounce" included in the name somewhere. And paste this in an other folder (will be on my Dropbox).
This works good. And Dropbox works better on CloudBeats. Now, the problem is that there will be A LOT of bounce-files (versions) in Dropbox, and I can not delete them to keep that folder fresh as that will only end up with a new copy next time the Hazel- workflow runs.

SO:
My idea is to do this copy, but as soon as the file has been copied, rename that source-file by replace "_bounce" to ex "-copied". This way it will never be copied twice...

Is this possible to do in Hazel? Or does any of you have any other idea I could try out?

Thanks!
/ Andreas

First off, the Forum/Site forum is for questions about the website. I've moved your topic to the appropriate forum.

The main issue is that after a copy action, any actions in the same rule apply to the copy. A couple ways to do this:

- Do the rename in another rule and use the Continue action in the original rule
- Use the "Sync" action which works like a Copy, but the actions after a Sync still apply to the original.

Thanks! And thanks for moving the post to where it belongs, sorry for that! I will try your ideas! Sounds logical to me.