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 static label or tag to all items passing through a workflow.
- Overwriting or setting a specific string property uniformly across multiple data entries.
- Testing or demonstrating how to manipulate item data within n8n workflows.
For example, if you want to mark all records with a status like "Processed" or add a note to each item, this node can be used to set that string easily.
Properties
| Name | Meaning |
|---|---|
| My String | The string value to assign to the myString field in each item's JSON data. This can be any text entered by the user. |
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 via the input property.
Output structure example for one item:
{
"json": {
"myString": "User provided string value",
// ... 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 internal n8n workflow data manipulation capabilities.
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 processing an item, the node either continues (if configured to continue on fail) or throws an error indicating the item index where the failure happened.
- Data type issues: Since the node expects a string input, providing non-string values (via expressions or variables) should be validated beforehand to avoid unexpected results.