I've found workflows to be extremely useful for any task that I want to schedule and/or automate. Obviously most tasks can be done through SQL scripting but this saves me (more often than not) the headache of trying to find all of the associations.
Some very simple workflows that have saved me a lot of time (that I created) include:
-A workflow that runs against all of our auto-registered Laptop backup clients to change their default prune after delete (-retentionRule).
-A workflow that can go in to every subclient on the CommServe and change a specific setting (for instance we had to change every client's -softwareCompression).
-A workflow that kills a job based on it's ID which I have implemented in to our Alerts to quickly kill pending jobs that we KNOW will fail to save the time/processing. (You can run Workflows as a trigger to any Alert you have active).
My next step is creating Workflows that will take you step-by-step to create a new Subclient(s) and another that will take you step-by-step to activate a Restore job. These are both relatively simple in Workflow and if you have Cloud services installed you can actually run them from your web console. Meaning I can kick off a Restore or create a new subclient from my phone.