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 label or tag 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 incoming records with a status like "Processed" or add a note, you can use this node to set that string on each item.
Properties
| Name | Meaning |
|---|---|
| My String | The string value to assign to the myString field on each input item. This can be any text the user wants to set. |
Output
The node outputs the same number of items as it receives, but each item’s JSON data will have a new or updated property called myString containing the string provided by the user.
Output structure example for one item:
{
"json": {
"myString": "User provided string"
// ... other original properties remain unchanged
}
}
No binary data output is produced by this node.
Dependencies
- No external services or API keys are required.
- The node relies solely on n8n's internal framework and standard input/output handling.
Troubleshooting
- Empty or missing input: If no input data is provided, the node will simply return an empty array.
- Invalid input types: Since the node expects input items with JSON data, non-JSON inputs may cause unexpected behavior.
- Error handling: If an error occurs during processing an item, the node either continues processing remaining items (if configured to continue on fail) or throws an error indicating the item index where the failure happened.