Appearance
Static Data
The Static Data node provides a hardcoded JSON array as pipeline input. Use it for configuration data, dropdown options, lookup tables, or any data that does not change at runtime.
Configuration
| Property | Type | Default | Description |
|---|---|---|---|
data | string (JSON) | [] | Required. A JSON array of objects. |
orderBy | string | -- | Column to sort results by. |
order | string | DESC | Sort direction: ASC or DESC. |
whereField | string | -- | Field to filter on. |
whereOp | string | = | Comparison operator: =, !=, >, <, >=, <=, LIKE. |
whereValue | string | -- | Value to compare against. |
limit | number | 100 | Maximum rows to return. |
offset | number | 0 | Number of rows to skip. |
Input
This is a source node -- it has no input port.
Output
Returns the parsed JSON array, optionally filtered, sorted, and paginated by the query options.
Example Data
json
[
{ "value": "red", "label": "Red", "hex": "#FF0000" },
{ "value": "green", "label": "Green", "hex": "#00FF00" },
{ "value": "blue", "label": "Blue", "hex": "#0000FF" }
]How It Works
- The
dataconfig is parsed from JSON into a PHP array. - Query options (
orderBy,whereField,limit,offset) are applied to the parsed data. - The resulting array is returned as the node output.
If the data value is already an array (not a JSON string), it is used directly.
Example Use Cases
Dropdown options for a select widget
json
[
{ "value": "small", "label": "Small" },
{ "value": "medium", "label": "Medium" },
{ "value": "large", "label": "Large" }
]Status configuration table
json
[
{ "key": "active", "label": "Active", "color": "green", "icon": "check" },
{ "key": "pending", "label": "Pending", "color": "yellow", "icon": "clock" },
{ "key": "inactive", "label": "Inactive", "color": "red", "icon": "x" }
]Navigation menu items
json
[
{ "title": "Home", "url": "/", "order": 1 },
{ "title": "About", "url": "/about", "order": 2 },
{ "title": "Contact", "url": "/contact", "order": 3 }
]TIP
Static Data is useful when combined with a Lookup node. Store lookup mappings as static data and join them onto dynamic query results for label resolution or configuration enrichment.