Node library
Reference for all 179 nodes across 16 categories in the DRAGOPS visual scripting engine.
The DRAGOPS node library contains 179 language-agnostic primitives organized into 16 categories. Each node performs a single, focused operation. You compose them by wiring pins together on the canvas to build automation patterns.
Category overview
| Category | Nodes | Description |
|---|---|---|
| Events | 8 | Triggers that start pattern execution |
| Flow Control | 24 | Branching, loops, error handling, and execution routing |
| Literals | 8 | Constant values — strings, numbers, booleans, objects |
| Variables | 7 | Read, write, and manipulate pattern variables and secrets |
| Math | 24 | Arithmetic, rounding, interpolation, and random numbers |
| Comparison | 10 | Equality, ordering, null checks, and type testing |
| Logical | 5 | Boolean logic and conditional value selection |
| String | 21 | Text manipulation, search, formatting, and regex |
| Object / Map | 13 | Property access, merging, and key-value operations |
| Array | 23 | Collection operations — map, filter, sort, group, zip |
| Type Conversion | 7 | Convert between types — string, number, boolean, JSON |
| Date / Time | 10 | Timestamps, formatting, arithmetic, and epoch conversion |
| HTTP | 6 | HTTP requests, responses, URL building, and form data |
| Data Formats | 7 | Parse and generate CSV, XML, YAML, and JSON |
| Encoding | 18 | Base64, hex, hashing, HMAC, encryption, and certificates |
Pure vs impure nodes
Every node in DRAGOPS is either pure or impure. This distinction controls how the node behaves in the execution flow.
Pure nodes
Pure nodes compute a value from their inputs without side effects. They have no execution pins — the engine evaluates them inline whenever a downstream node needs their output.
Examples: Add, Concat, Get Property, Equal, Now.
Impure nodes
Impure nodes perform actions that change state or interact with external systems. They have execution pins (the triangular connectors on the left and right) that determine when the node runs in the sequential flow.
Examples: HTTP Request, Log, Set Variable, Branch, For Each.
Node header colors
Every node has a colored header that indicates its role at a glance:
| Header color | Role | Examples |
|---|---|---|
| Pink | Event | On Webhook, On Schedule, On Error |
| Blue | Function | Add, Concat, Get Property, Equal |
| Orange | Flow | Branch, For Each, Switch, Sequence |
| Green | Action | HTTP Request, Log, Set Variable |
Integration pack nodes
Integration packs add service-specific nodes to the library. Pack nodes appear alongside built-in nodes and work the same way — drag, wire, run. Each pack node maps input pins to an HTTP request and output pins to the response, so you do not need to configure the HTTP call manually.
See available integration packs for the full list.
Finding nodes
The node library panel at the bottom of the editor shows all available nodes organized by category. Use its search bar or browse the category tree to find what you need.
You can also right-click on the canvas to open a quick search menu. Type a node name, category, or alias. Many nodes have multiple aliases — for example, you can find Branch by searching "if", "conditional", or "?".
To find a node already placed on the canvas, press Cmd+F (macOS) or Ctrl+F (Windows/Linux).