Variablen und Ausdrücke

Während eines Laufs behält Knot einen JSON-Kontext bei: vorherige Knoten-Ausgaben, Trigger-Metadaten und globale Variablen. Sie lesen es mit Moustache Ausdrücken „[object Object]“.

💡 Kontextfluss

Each node reads the accumulated context and adds its own output (key usually derived from the node id).

💡 Mustache syntax

Pattern	Usage
{{ nodes.<id>.field }}	Output field from a node
{{ trigger.payload.x }}	Trigger input data
{{ entity }}	Current Dolibarr entity (multi-entity)

Example in an HTTP body or email field:

{
  "subject": "Reminder {{ nodes.fetch_invoice.ref }}",
  "to": "[email protected]"
}

Simulieren

In Simulate, the same expression engine evaluates fields with your test data — no Dolibarr writes.

💡 Common patterns

• Concatenation: multiple {{ }} in one string.
• Conditions: prefer a Logic node (If/Else) over complex inline logic.
• Defaults: stub values in Simulate to avoid empty fields while designing.

💡 Good practices

1. Rename nodes clearly in the editor — easier to find nodes.* keys.
2. Never store secrets in plain text — use encrypted credentials for API tokens.
3. Simulate every branch before activating the workflow.

💡 See also

• Nodes and edges
• HTTP connectors (details coming soon)