# How to structure your flows

**URL:** <https://community.homey.app/t/how-to-structure-your-flows/25109>\
**Category:** Flows\
**Created:** [January 27, 2020, 10:31pm UTC](https://community.homey.app/t/how-to-structure-your-flows/25109 "2020-01-27T22:31:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [January 27, 2020, 10:31pm UTC](https://community.homey.app/t/how-to-structure-your-flows/25109/3 "2020-01-27T22:31:23Z")

</div>

**How to structure flows: keep flows simple**

After working a lot with flows I currently have the habit of splitting up my flows.

My personal motto is: more flows is not bad!

I use A few “types” of flows and try not mix these types in one flow (explained in more detail below)

I also use a “tag” in the naming of the flow, so I can easily recognize the type (inspired by @AcE_Krystal a few years ago)  
Update: or use icons as described by @Ploegske in the responses [below](https://community.homey.app/t/how-to-structure-your-flows/25109/29)

**My flow types:**

- _Trigger flow_: a flow triggered by a time event (tag: **@** or 🕐) or a sensor (tag: \*\*!\*\*or 📳)

Examples for naming: @ 06:50 get out of bed, ⏱ dinertime, ! Lux kitchen, 📳 PIR kitchen

WHEN typically contains a trigger like time or sensors like motion, temp, etc.

THEN typically contains a card from the flow section: “start flow” / “enable flow” / “disable flow” or change the status of a virtual devices.

THEN typically _does not_ contain cards for actual devices (lights, plugs etc).

Time triggered flows (tag: @/⏱) will often have multiple cards in the THEN

- _Action flow_: flow that starts an action (Tag: **\>** or 🚀)

Examples for naming: \> Radio ON, 🚀 lights living OFF

WHEN typically contains a card “when this flow is started” or a virtual device status change

THEN contains an action: switching devices or starting a scene flow (explained below)

- _Scene flow_: flow that defines a “scene” or “mode” (tag: **#** or 💡)

Examples of naming: 💡 kitchen bright, # movie time light living, # Alarm armed modus, # Holiday modus

WHEN contains a “when this flow is started” or a virtual device button (not a switch!)

THEN contains settings for a group of devices, lights etc in a specific zone

Keep scene flows specific to one zone that makes it easier to use them in multiple flows.

---

_[View the full topic](https://community.homey.app/t/how-to-structure-your-flows/25109)._