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 assigns it to a field called myString on every incoming data item. This node is useful for scenarios where you want to annotate or tag data items with a custom string value, such as adding a label, note, or identifier before passing the data downstream.
Practical examples:
- Adding a status message or comment to each record in a workflow.
- Tagging data items with a batch name or processing step description.
- Injecting a fixed string value into all items for later filtering or routing.
Properties
| Name | Meaning |
|---|---|
| My String | The description text; a string value that will be assigned to the myString field of each input item. |
Output
The output consists of the same array of items received as input, but each item's JSON data will have a new or updated property named myString set to the value provided by the user.
- json: Each item’s JSON object includes a
myStringproperty containing the user-defined string. - No binary data is produced or modified by this node.
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
myStringproperty on any item, the node either continues processing remaining items (if configured to continue on failure) or throws an error indicating the item index where the failure happened. - Common issues:
- Providing non-string values or leaving the string empty may not cause errors but could lead to unexpected results downstream.
- Ensure that the input data is properly formatted JSON objects; otherwise, the assignment might fail.