
Nodes Properties
Getting Started
Examples
Simulations
Connections
Advanced Nodes
Nodes Properties
Custom Variables
Collaboration
Accounts
Unity Plugin (UP) & API
Evolution
Trigger Modes
In the video above the terminology used is different than what it’s currently used in the app and in the documentation.
Activation Modes = Trigger Modes
On Start = Enabling
However, the functionalities presented in the video are on par with the current version of machinations.io
Nodes have 4 Trigger Modes, according to which Resources get redistributed.
Set the Trigger Mode of a Node in its Functional menu, under Trigger.
When a Node fires it pushes or pulls Resources along the Resource Connections that are connected to it. Whether a Node fires depends on its Trigger Mode.
A Node in a Machinations diagram can be in one of 4 different Trigger Modes:
- Passive – can fire only in response to a trigger generated by another element
- Interactive – fires only when clicked on, during Play (not during Batch Plays)
- Automatic – fires every Step. All automatic Nodes fire simultaneously
- Enabling – fires once, immediately after you click the Play button, AND any time a condition is met

Interactive Nodes fire after being clicked when the next Step begins. This may make it seem as if the Node didn’t receive the input or that there’s a delay.
Interactive Nodes are only clickable during Interactive Play. During Batch Plays, they are treated as passive Nodes.
🔧 Here are 3 examples of Trigger Modes, and their actions (or lack thereof).
- In the Push example, the Blue, Orange, Green and Red Pools are set to push a Resource at any Step their Trigger Mode is met
- In the Pull example, the 4 coloured Pools are set to pull a Resource at any Step their Trigger Mode is met.
- The Triggered example showcases how another Node on the diagram can act as an activator.
Enabling example: The Source will fire at the beginning of the Play AND thereafter every time the Enabling Condition (Enabler >0) is met.
In the example below, both the Source and the Pool are set to automatic. This will double the flow of Resources, as both Nodes will perform an action during a given Step. So instead of 1 Resource flowing from the Source to the Pool, as stated on the Resource Connection Label, 2 Resources will be transferred during one Step.
You may want to check out: