04. Action & Trigger Nodes
- Node - a part of the scenario that defines a specific action or trigger.
- Node - a component of the scenario connected by routes to other nodes, executed sequentially according to its placement in the scenario.

There are two types of nodes:
- Triggers (1) nodes initiate and control the start of scenario execution.
- Actions (2) nodes are responsible for processing data, making requests, retrieving data, and handling response statuses.

The list of all available nodes is displayed for selection in the Choose an app window after clicking the button to add a new node.
There are several system nodes, and some of them are grouped:
- Trigger on Webhook - a node for triggering the scenario through a webhook request.
- Trigger on Schedule - a node for scheduling scenario execution.
- Trigger on Run once - a node for running the scenario by clicking the Run Once button.
- Webhook response - a node for returning a response upon scenario execution.
- HTTP Request - a node facilitating request transmission.
- Group of nodes Code - nodes handling data processing and output formation.
- Group of nodes Tools - nodes providing special features during scenario execution, such as iterative data processing or recording values as variables.