When triggering a manual flow, we currently have 3 options:
Specific record
Number of records
All records
In many cases, I would like to run an automation on a specific view of records. I can set up a separate flow to trigger on the view, but this doesn’t work as well if the view has a lot of records.
My only solution is to trigger the flow manually on all records, ensuring that the flow has the same filter conditions as the view I want. This is less efficient for everybody, since now the flow has to check every single item which takes a long time and puts unnecessary strain on the system.
I would love a fourth option to trigger the automation on a view. This way I can run the flow on the specific items I need and save time/resources.
oooh yes, I have wished for this many times!
I often end up with ‘junk’ automations floating around that were just used once to ‘get a view’ then either call a manual automation, or update a certain trigger field on all items within that view to cause this ‘manual run’ of an automation.
That’s my route exactly as well! It’s alright, but becomes tedious when working with a lot of records. I also believe the triggering flow can time out if I trigger on a view with several thousand items, so then you have to get more creative and create extra fields to track which records the flow has already run on.
Great idea! When I read this, I realized how useful it would be. A view-based manual flow would save our team a lot of time, since we often build a lot of filters just to recreate what already exists in a view. That would be great!
Saw this in the latest posts.
If I understand it correctly, the idea is that I can create a view in an app, similar to how I would use views for dashboards, and then use that view as the starting point for a manual run. If that’s right, it would help a lot.
