Executors

The Executor is a container node that organizes executor child nodes. When triggered, it propagates execution to its children — such as Logic Gate, Outgoing Webhook, Lambda, Calculation, or Compute. Executors perform actions, calculations, or side effects in response to triggers or data changes.

Info: Executors are the action half of Krill automation: Triggers decide when something happens, Executors decide what happens.

Overview

In Krill, automation reads as a tree. A Data Point or Trigger sits at the top; beneath it, an Executor container holds one or more action nodes. When the parent fires, the Executor passes that execution signal down to each child, letting you group several actions under a single condition.

How It Works

graph TD
    A[Parent fires - Trigger or DataPoint] --> B[Executor container]
    B --> C[Calculation]
    B --> D[Logic Gate]
    B --> E[Outgoing Webhook]
    B --> F[Lambda]

1. A parent trigger or data point executes.
2. The Executor container receives the execution signal.
3. It propagates execution to every child executor in turn.
4. Each child performs its specific action — a formula, a boolean evaluation, an HTTP call, a Python script, and so on.

Executor Types

Executor	Action
Calculation	Compute derived values with formulas
Compute	Run server-side computation
Logic Gate	Evaluate boolean logic (AND, OR, XOR, …)
Lambda	Execute Python on the server
Outgoing Webhook	Send an HTTP request to an external service
SMTP	Send an email alert

Use Cases

• Group actions under a trigger so several things happen together.
• Organize automation logic into readable, reusable branches.
• Chain multiple executors to build multi-step workflows.

Examples

• Add actions to run when this trigger fires.
• Create an executor group for this data point.
• Organize my automation actions under this trigger.

Related

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

---

Last verified: 2026-05-21