Overview
This node, named "Example Node," is a basic transformation node designed to add or modify a string property in each input item. It takes an input data array and for each item, it sets the myString field in the JSON data to a user-defined string value. This node is useful when you want to annotate or tag your data items with a custom string, for example, adding a label, note, or identifier to each record passing through the workflow.
Practical examples:
- Adding a status message or comment to each data item.
- Tagging records with a specific category or batch name.
- Injecting a constant string value into all items for downstream processing.
Properties
| Name | Meaning |
|---|---|
| My String | A user-defined string value that will be assigned to the myString field of each item's JSON data. |
Output
The output is an array of items where each item's JSON data includes the myString property set to the value provided by the user. The structure of each output item is:
{
"json": {
"myString": "user defined 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 within the workflow.
Troubleshooting
Common issues:
- If the input data is empty or not properly formatted as an array of items, the node will simply return the input without modification.
- If the user does not provide a value for "My String," the node will set the
myStringfield to an empty string.
Error handling:
- If an error occurs during processing an item, and the node is configured to continue on failure, the error details will be attached to the output item under an
errorproperty. - Otherwise, the node throws an error indicating which item caused the failure.
- If an error occurs during processing an item, and the node is configured to continue on failure, the error details will be attached to the output item under an