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 in the data with a fixed string.
- Simple data enrichment where a static label or note needs to be attached to each item.
For example, if you want to tag all records with a status message or a category name, you can use this node 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. Users enter any text here; it will be added or overwrite the existing value in each item. |
Output
The output consists of the same number of items as the input. Each output item contains the original JSON data with an additional or updated property:
{
"myString": "user provided string"
}
No binary data is produced by this node.
If an error occurs during processing an item and the node is configured to continue on failure, the output for that item will include an error field describing the issue alongside the original JSON.
Dependencies
- No external services or API keys are required.
- This node operates purely on the input data within the workflow.
Troubleshooting
- Error Handling: If an error occurs while setting the string on an item, and the node is not set to continue on failure, the execution will stop and throw an error indicating which item caused the problem.
- Empty Input: If no input data is provided, the node will simply return an empty array.
- Incorrect Property Name: Since the property name
myStringis hardcoded in the node, changing the input property name without updating the node code will have no effect.