Feature Request: Dynamic date placeholders for destination paths (e.g., YYYY-MM)

[dannyneumann]

Hi
I’m currently migrating some of my file automation workflows from Hazel to Forel. One of my essential workflows is keeping my downloads clean by automatically moving files into monthly archive folders (e.g., ~/Downloads/Backup/2026-07/).
Right now, I have to use a custom Zsh script with mkdir -p to achieve this. It would be a massive quality-of-life improvement if the native "Move" action supported dynamic date tokens/placeholders (like {{year}}-{{month}} or %Y-%m) directly in the destination path.
Ideally, if the dynamic subfolder doesn't exist yet when the rule triggers, Forel would just create it automatically before moving the file.
This is a super common pattern for sorting receipts, logs, or daily downloads, and having it as a native feature would make Forel even more powerful.
Thanks for the great work on this project!

[lguichard]

Thanks a lot for the feedback! That's a really interesting feature to explore, and I can definitely see your use case being valuable for many other people as well. I've added it to the roadmap for consideration.

Since you're coming from Hazel, I'd also love to hear if you've noticed anything else that's missing or could be improved. Are there any other features or workflows you rely on in Hazel that you feel Forel should support?

[dannyneumann]

Thanks for the quick feedback!
Besides the folder actions, I actually only have one other main workflow: automatically opening applications when a specific file is added.
For example: I download a Citrix connection file (*.ica) via my browser, which goes into the Downloads folder. I would then set an action to check if a *.ica file exists in that folder, and if so, automatically open it (basically just a simple open FILENAME).
If Forel could support something like that, it would be awesome!

[lguichard]

@dannyneumann Open application action added in latest version ;-)