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 records with a status like "Processed" or add a note "Checked by QA", this node can do that easily by setting the myString property accordingly.
Properties
| Name | Meaning |
|---|---|
| My String | The string value to set on each item's myString field. This can be any text entered by the user. |
Output
The output consists of the same number of items as the input. Each output item contains the original JSON data with an added or updated property:
{
"myString": "<user-provided string>",
...original properties...
}
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 within the workflow.
Troubleshooting
- Empty or missing input: If no input data is provided, the node will output an empty array.
- Errors during execution: If an error occurs while setting the property (unlikely in this simple case), the node either stops execution or continues based on the "Continue On Fail" setting.
- Incorrect property name: Since the property name is fixed (
myString), ensure downstream nodes expect this field or adjust accordingly.