Dummy Data

Type key: dummy_data_node
Group: Data
Category: data
Tier: CORE

The Dummy Data node injects static or template-rendered data into the workflow. It is primarily used during development and testing to simulate the output of an upstream node without running the real service.

Handles

Handle	Direction	Description
input	Input	Optionally receives context for {{tag}} resolution
output	Output	Emits the configured data

Configuration

Field	Type	Default	Description
data_type	enum	json	Format of the configured content: json, text, csv
content	string	""	The data to emit; supports {{tags}}

Data Types

json

The content field must contain valid JSON. The parsed object/array is emitted directly.

{
    "data": [
        { "id": 1, "name": "Alice", "email": "alice@example.com" },
        { "id": 2, "name": "Bob", "email": "bob@example.com" }
    ]
}

text

The content is emitted as a plain string in a { "text": "..." } wrapper.

csv

The content is parsed as CSV and emitted as an array of objects (first row = headers).

id,name,email
1,Alice,alice@example.com
2,Bob,bob@example.com

Output:

{
    "data": [
        { "id": "1", "name": "Alice", "email": "alice@example.com" },
        { "id": "2", "name": "Bob", "email": "bob@example.com" }
    ]
}

Template Tag Support

The content field resolves {{tags}} from the execution context before parsing. This means you can inject dynamic values even in test data:

{
  "user_id": {{input.id}},
  "timestamp": "{{now}}",
  "environment": "test"
}

Use Cases

Dummy Data feeding a Filter node

💾 Try this example

Download the workflow JSON — open an empty workflow and import the file.

Dummy Data feeding a Validate Schema node

💾 Try this example

Download the workflow JSON — open an empty workflow and import the file.

Dummy Data feeding an Expression node

💾 Try this example

Download the workflow JSON — open an empty workflow and import the file.

Mocking an External API

Replace an HTTP Request node with Dummy Data while developing downstream logic:

{
    "choices": [
        {
            "message": {
                "content": "This is a mock AI response for testing purposes."
            }
        }
    ],
    "usage": { "total_tokens": 42 }
}

Providing Test Records

When you don't want to query the real database during development:

{
    "data": [
        { "id": 1, "order_total": 500, "status": "completed" },
        { "id": 2, "order_total": 1200, "status": "completed" }
    ]
}

Hardcoded Lookup Table

Inject static configuration that downstream nodes can reference:

{
    "vat_rates": {
        "IT": 0.22,
        "DE": 0.19,
        "FR": 0.2
    }
}

Notes

• The Dummy Data node is intended for development/staging. In production, replace it with real data nodes
• If data_type: json and the content is not valid JSON, the node returns a parse error
• {{tags}} are resolved before JSON parsing — ensure the replaced values produce valid JSON
• The node does not filter or modify its input — output is entirely determined by the content field