How to loop Flows in Directus

Directus is a super powerful data platform, and as you work with it more it's true power can be realized. In Short Hops, our team provide quick insights in how to get the most from Directus.
More episodes on Directus TV: directus.io/tv...

[@kickwriteteach2313]

it would be helpful also if this were in some kind of writeup. I find videos difficult to follow and (for most things) prefer written docs

[@tilakrajchoubey5534]

Can we perform the loop operation with the create operation?

[@EasyViber]

When you need a 6+ minute tutorial for such a basic use case, you know that Directus has to solve this in an easier way (some kind of forEach node)?

[@TheMaxiviper117]

Seriously considering replacing a Zoho CRM project with directus, almost does everything it can do.
Is there a way to conditionally hide or show Flows on a Collection page based on something like a dropdown field's value (e.g. Deal stage), then have a particular flow show up conditionally to act as a transition button to update the fields value to the next "deal" stage value (e.g. Deal Won) but only if certain inputs are filled via confirmation inputs. (in which case could we also conditionally show certain confirmation inputs).
Looking for how I could replicate Zoho Blueprint transitions.

[@DirectusVideos]

Do it!
We don't currently have support to show or hide the manually trigger flows for a collection. But you could try something like this extension - github.com/rezo-labs/directus-extension-api-trigger-interface - which is an interface that allows you to trigger API calls within the form itself - which you could potentially apply conditional logic to.

[@TheMaxiviper117]

@@DirectusVideos Thanks will have a look

[@def5yes]

why are these two different flows not one? doesnt make any sense, only if it the second flow would be re-usable, but its not even dynamic, so makes no sense..

[@DirectusVideos]

All down to that trigger at the start - the second flow has a trigger of "another flow".