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 for this node include:
- Adding a constant or user-defined string value to all items passing through a workflow.
- Overwriting or initializing a specific field with a fixed string before further processing.
- Testing or debugging workflows by injecting known values into the data stream.
For example, if you want to tag all incoming data items with a specific label or note, you can use this node to set that label uniformly.
Properties
| Name | Meaning |
|---|---|
| My String | The description text; a string value to assign to the myString field in each item's JSON data. |
Output
The node outputs the same number of items as it receives. Each output item contains the original JSON data with an added or updated property:
{
"myString": "<value provided in the node parameter>"
}
No binary data is produced by this node.
Dependencies
- No external services or API keys are required.
- This node relies solely on n8n's internal framework and standard node execution context.
Troubleshooting
- Empty or missing
myStringvalue: If the input string is left empty, the node will set themyStringproperty to an empty string, which might not be intended. Ensure the property is filled correctly. - Errors during execution: If an error occurs while setting the property, the node either continues processing subsequent items (if configured to continue on failure) or throws an error indicating the item index where the failure happened.
- Input data format: The node expects input items to have JSON data. Supplying non-JSON or malformed data may cause unexpected behavior.