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 the myString field of every incoming data item. This node is useful when you want to annotate or tag your data items with a consistent string value, such as adding a label, note, or identifier.
Practical examples:
- Adding a status message or category label to all records before further processing.
- Injecting a constant string value into each data item for downstream filtering or routing.
- Testing workflows by appending a known string to verify data flow.
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 node outputs the same number of items as it receives as input. Each output item contains the original JSON data with an added or updated property:
json.myString: Set to the string provided in the "My String" input property.
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
Common issues:
- If the input data is empty or not structured as expected, the node will still run but simply add the
myStringproperty to whatever JSON exists. - Errors during execution typically relate to invalid input data or internal errors.
- If the input data is empty or not structured as expected, the node will still run but simply add the
Error messages:
- If an error occurs on a specific item, and the node is configured to continue on failure, the output will include an error object alongside the item’s JSON.
- Otherwise, the node throws an error indicating the item index where the failure happened.