Frequently Asked Questions

Does FileFlow require root access?

No, FileFlow does not require root access to function.

What permissions does FileFlow need and why?

FileFlow dynamically requests read and write permissions for directories involved in the rules you create. Other permissions may be used by libraries to manage tasks, such as periodic background execution of rules.

Additionally, the following permissions are included in the app manifest but only utilized when granted/triggered by the user:

• REQUEST_IGNORE_BATTERY_OPTIMIZATIONS - to request exemption from background usage restrictions
  • Unrestricted background execution lets FileFlow execute rules exactly according to their schedules.
• WRITE_EXTERNAL_STORAGE/MANAGE_EXTERNAL_STORAGE - for targeting protected locations

Some builds (debug, nightly, and releaseWithNetwork) also contain the following permissions:

• INTERNET - to connect to SFTP servers, to perform "remote" actions

What are some use-cases for FileFlow?

Personally, I use the MOVE action to re-organize files exported from various FOSS apps I use. They all have their own conventions and flavors, but I need a standard format for mirroring/cloud backups. This is what FileFlow is made for.

1. AntennaPodBackup-\d{4}-\d{2}-\d{2}\.db 🠂 antennapod.db
2. Loop Habits Backup \d{4}-\d{2}-\d{2} \d{6}\.db\.bin 🠂 habits.db
3. TubularData-\d{8}_\d{6}\.zip 🠂 tubular.zip

Also, the DELETE_STALE action helps clean up single-use downloads, like APKs.

4. .*apk after 30 days