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 sets this string as the value of the myString field on every incoming data item.
Common scenarios where this node is useful include:
- Adding a constant or user-defined tag or label to all items passing through a workflow.
- Overwriting or setting a specific string property uniformly across multiple data items.
- Simple data enrichment or annotation before further processing.
For example, if you want to mark all records with a status like "Processed" or add a note such as "Reviewed by QA", this node can do that easily.
Properties
| Name | Meaning |
|---|---|
| My String | The string value to set on each item's myString field. This can be any text entered by the user. |
Output
The output consists of the same array of items received as input, but each item’s JSON data will have its myString property set or overwritten with the user-provided string.
Output structure example for one item:
{
"json": {
"myString": "User provided string"
// ... other original properties remain unchanged
}
}
No binary data is produced by this node.
Dependencies
- No external services or API keys are required.
- This node operates purely on the input data within the workflow.
Troubleshooting
- Empty or missing input: If no input data is provided, the node will simply return an empty array.
- Errors during execution: If an error occurs while setting the property (unlikely in this simple case), the node either continues processing subsequent items if configured to continue on failure or throws an error indicating the item index.
- Incorrect property name usage: Since the property name is fixed (
myString), ensure downstream nodes expect this field or adjust accordingly.