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.
- Injecting a constant string value into data for further processing or filtering downstream.
- Testing or debugging workflows by appending known values to data items.
For example, if you want to mark all records with a status like "Processed" or add a note "Checked by QA", this node can be used to set that string uniformly.
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 n8n's internal framework and standard input/output handling.
Troubleshooting
- Empty or missing
myStringvalue: If the input string is left empty, the node will still set themyStringproperty to an empty string, which might not be intended. Ensure to provide a meaningful string. - Errors during execution: If an error occurs while setting the property, the node supports continuing on failure if enabled; otherwise, it will throw an error indicating the item index where the failure happened.
- Input data format: The node expects input items to have JSON data. If input items lack JSON or are malformed, errors may occur.