Static Data

Description

The staticdata module allows injecting predefined static data into the workflow flow. It is useful when you need to start a flow with fixed data that does not come from an external trigger, or when you want to combine static data with other nodes. It accepts data in JSON format (object or array) configured directly in the node. If the data is a JSON string, it is automatically parsed. It is commonly used to define configurations, value lists, templates or test data.

Configuration

Parameter	Type	Required	Description
data	text	Yes	Static data in JSON format (object or array) that will be injected into the flow.

Output

{
  "nextModule": "siguiente_modulo",
  "data": { "clave1": "valor1", "clave2": "valor2" }
}

Usage Example

Basic case

{
  "label": "Static Data",
  "data": "{\"paises\": [\"ES\", \"MX\", \"AR\"], \"moneda\": \"EUR\"}"
}

Notes

• If data is a valid JSON string, it is automatically parsed to object or array.
• If JSON parsing fails, an error is returned with nextModule: null instead of throwing an exception.
• Supports both objects and arrays as input data.
• This node accepts input connections (target), so it can be used as an intermediate node, not only as a start.
• It is an alternative to the Start node when fixed data without a trigger is needed.

Related Nodes

• Start (basic trigger with optional data)
• setVariable (to store data in variables)
• mapper (to transform data)