Overview
This node, named "Example Node," is a basic transformation node designed to add or overwrite a string property in each input item’s JSON data. It takes an input string from the user and assigns it to a field called myString on every incoming data item. This node is useful for simple data enrichment or tagging scenarios where you want to append a consistent string value to all items passing through the workflow.
Practical examples:
- Adding a fixed label or category name to each data item.
- Injecting a constant identifier or note into records before further processing.
- Testing workflows by appending a known string to verify data flow.
Properties
| Name | Meaning |
|---|---|
| My String | The description text; any string value to assign to the myString field of each item. |
Output
The output consists of the same number of items as the input. Each item's JSON data will have a new or updated property named myString set to the value provided in the node's input property.
No binary data is produced by this node.
Example output JSON structure per item:
{
"myString": "value set by user",
// ... other original properties remain unchanged
}
Dependencies
- No external services or API keys are required.
- This node operates purely on the input data within the workflow.
Troubleshooting
Common issues:
- If the input data is empty or not structured as expected, the node will simply pass through the data without modification.
- Errors during execution typically relate to invalid input types or unexpected data structures.
Error messages:
- If an error occurs on a specific item, and the node is configured to continue on failure, the error details will be attached to that item’s output under an
errorproperty. - Otherwise, the node throws an error indicating the item index where the failure happened.
- If an error occurs on a specific item, and the node is configured to continue on failure, the error details will be attached to that item’s output under an