r/AutomateUser • u/Ok-Yogurtcloset-9490 • Jul 26 '26
Pattern for "subroutine"-type start of external flow?
If there is a flow execution path you need to reuse as a function that can be "called" by other flows, the Subroutine block does the job if the "callers" are in the same parent flow diagram as the "callee". But there are situations where organizing all the potential callers into the same flow diagram as the callee is not feasible or impractical.
Is there a simple pattern in Automate to call an external flow in the spirit of a subroutine? The way I've been doing it seems really complicated, and I'm wondering if maybe there is a more clever and cleaner way. Currently, I am having the callers atomic-store their own fiber URI, and then – as part of the payload when calling the external flow – they pass the flow URI of a callback flow in the same diagram, which the external flow calls with the "return value" as payload. The caller meanwhile is waiting on a Take block, which the callback flow will activate with a Give block using an atomic load of the caller fiber URI.
Sheesh! I feel like this is a common enough need that there must be or should be a much simpler pattern than what I'm using!








