Hi,
There are two main reasons to use flow designer:
1) When the logic of an activity is largely sequential, A -> B -> C, with few if any logic branches. Then, flow designer is a quick and easy way to create and test workflow.
2) Certain stakeholders will prefer or require no-code methods for creating common logic. For instance, trigger a notification for a specialized reason or for data cleansing. This can be an easy way to delegate work to the SME most familiar with a process and the data. Basically, you can think of Flow Designer as a no-code way to do a scheduled job to process data in a batch fashion or a business rule to trigger some workflow; and even standard integrations using integrationHub.
I would suggest you to check the following interesting documentation, it might be useful for understanding when you should use Flow Designer and use it in the right way:
Best practices for using the Flow Designer
If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.
Thank you
Cheers
Alberto
