Triggers

The Trigger is a container node that organizes trigger child nodes under a Data Point. When executed, it retrieves the upstream Data Point value and runs all of its child triggers. The specific behavior is implemented by children such as High Threshold, Low Threshold, Cron Timer, Button, Silent Alarm, or Incoming Webhook.

Info: Triggers are the decision half of Krill automation: a Trigger decides when to act, and its child Executors decide what to do.

Overview

Every Krill automation answers two questions: when? and what? The Trigger container answers the first. Placed under a Data Point, it watches that data stream and fires its child triggers — evaluating thresholds, schedules, or external events — which in turn execute downstream Executors.

How It Works

graph TD
    A[DataPoint updates] --> B[Trigger container]
    B --> C[High Threshold]
    B --> D[Low Threshold]
    B --> E[Cron Timer]
    B --> F[Incoming Webhook]
    C --> G[Executors run]

1. The parent Data Point receives a new value.
2. The Trigger container retrieves that upstream value.
3. It propagates execution to each child trigger.
4. A child whose condition is met fires, executing its own child Executors.

Trigger Types

Trigger	Fires when
High Threshold	Value rises above a limit
Low Threshold	Value falls below a limit
Cron Timer	A schedule elapses
Button	A user presses it
Silent Alarm	Expected data stops arriving
Incoming Webhook	An external HTTP request arrives
Color	A color value enters a target range

Use Cases

• Group multiple triggers under a single Data Point.
• Organize threshold and alarm logic for one sensor in one place.
• Monitor a sensor with several conditions at once.

Examples

• Add a trigger to this temperature sensor.
• I want to be alerted when this value changes.
• Set up monitoring on this data point.

Related

• Executors
• Data Points
• How Nodes, Verbs, and Sources Work

---

Last verified: 2026-05-21