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 or user-defined string to all items passing through a workflow.
- Overwriting or setting a specific field with a constant value for downstream processing.
- Simple data enrichment or tagging within a workflow.
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 in the myString field.
Properties
| Name | Meaning |
|---|---|
| My String | The description text; any string value to assign to the myString field in each item. Placeholder shown as "Placeholder value". |
Output
The output consists of the same number of items as the input. Each item's JSON data will have a new or updated property called myString set to the string provided by the user.
Output structure example for one item:
{
"myString": "user provided string",
// ... other original properties remain unchanged
}
No binary data is produced by this node.
Dependencies
- No external services or API keys are required.
- This node operates purely on the input data it receives within the workflow.
Troubleshooting
- Error Handling: If an error occurs while setting the
myStringproperty on an item, the node either continues processing subsequent items (if configured to continue on fail) or throws an error indicating which item caused the failure. - Common Issues:
- Providing non-string values or leaving the string empty may result in unexpected outputs but will not cause errors.
- Ensure that the input data is valid JSON objects; otherwise, the node might throw errors when trying to assign the property.