# \[Feature Request\] See flow dependencies

**URL:** <https://community.homey.app/t/feature-request-see-flow-dependencies/43420>\
**Category:** Ideas & Suggestions\
**Created:** [February 21, 2021, 12:10pm UTC](https://community.homey.app/t/feature-request-see-flow-dependencies/43420 "2021-02-21T12:10:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Niclas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/niclas/32/13339_2.png) [@Niclas](https://community.homey.app/u/Niclas)\
**Post date:** [February 21, 2021, 12:10pm UTC](https://community.homey.app/t/feature-request-see-flow-dependencies/43420/1 "2021-02-21T12:10:13Z")

</div>

When you have a lot of flows, where some of them calls another flow, it would be great if there was a way to see which flows that calls a specific flow. For example it would be helpful, if you edit a flow, there was a way to see in a list which flow or flows that calls this flow.  
Even better would be if there was a visual map of flow dependencies.

Here’s an example of what the visual map would look like:

Flow A  
Flow B → Flow C → Flow D  
Flow C → Flow D  
Flow D  
Flow E → Flow F  
-------------\> Flow G

As an explanation to the above map:  
Flow A calls no flow  
Flow B calls flow C, which in its turn calls flow D  
Flow C calls flow D  
Flow D calls no flow  
Flow E first calls flow F and then calls flow G

Niclas

---

<div class="post-metadata">

**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\
**Post date:** [July 30, 2021, 7:43pm UTC](https://community.homey.app/t/feature-request-see-flow-dependencies/43420/2 "2021-07-30T19:43:26Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![FKey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fkey/32/14793_2.png) [@FKey](https://community.homey.app/u/FKey)\
**Post date:** [July 31, 2021, 7:18am UTC](https://community.homey.app/t/feature-request-see-flow-dependencies/43420/3 "2021-07-31T07:18:49Z")

</div>

Just added a 💚 +1 on this.  
Really miss this too.

But must say. I found a workaround that even brings some advantages:  
(See also my posting “[how to structure your flows](https://community.homey.app/t/how-to-structure-your-flows/25109)”)  
For flows that I know I will call from other flows: I create a virtual device pushbutton and use that as a trigger (instead of “when this flow is triggered”)  
Virtual device do show flow dependencies…

When you create a new flow that is triggered by another flow, you do not need to go to the the other flow to add the “trigger this flow”  
Just stay in your new flow and find that virtual device button…

And you can even trigger that same virtual button at different times…

This is the virtual button showing the flows its triggering:

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/e/2e7416eb0407053a163cc6cc1eb2fe8fba547c16.jpeg)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/2/125fa373a18b808236d38aedbb0d31fda826b37f.jpeg)

I trigger the same button at different times  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/4/8468ee395dea771ab54c0bb800c8fef9c96e09bb.png)  
Sleeping in on sundays…  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/b/dbc4480d6e12aaefb7b8ec4988c1ed2eb6d5d50b.png)

---

<div class="post-metadata">

**Author:** ![Undertaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/undertaker/32/53278_2.png) [@Undertaker](https://community.homey.app/u/Undertaker)\
**Post date:** [July 31, 2021, 7:20am UTC](https://community.homey.app/t/feature-request-see-flow-dependencies/43420/4 "2021-07-31T07:20:28Z")

</div>

+1 👍

---

<div class="post-metadata">

**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\
**Post date:** [July 31, 2021, 10:18am UTC](https://community.homey.app/t/feature-request-see-flow-dependencies/43420/5 "2021-07-31T10:18:32Z")

</div>

> [@FKey](#):
>
> I found a workaround

It is a useful workaround for same things, but with hundreds of flows and already hundreds of real devices, things would explode pretty fast. This was also why I was happy about Google Home activation of flows, even though I don’t like that it is linked to favorites and not some other flag.

---

<div class="post-metadata">

**Author:** ![Niclas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/niclas/32/13339_2.png) [@Niclas](https://community.homey.app/u/Niclas)\
**Post date:** [July 31, 2021, 10:52am UTC](https://community.homey.app/t/feature-request-see-flow-dependencies/43420/6 "2021-07-31T10:52:43Z")

</div>

The request still stands, but thanks for the workaround! I will definitely have a look at that.

Niclas

---

<div class="post-metadata">

**Author:** ![Chuck](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chuck/32/146201_2.png) [@Chuck](https://community.homey.app/u/Chuck)\
**Post date:** [October 2, 2026, 4:38pm UTC](https://community.homey.app/t/feature-request-see-flow-dependencies/43420/7 "2026-10-02T16:38:55Z")

</div>

+1
