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. This node is useful when you want to annotate or tag data items with a specific string value, for example, adding a status label, a category tag, or any custom note to each item passing through a workflow.
Practical examples:
- Adding a fixed comment or label to all records before sending them to another system.
- Tagging data items with a batch identifier or processing step name.
- Overwriting or setting a specific field uniformly across multiple data entries.
Properties
| Name | Meaning |
|---|---|
| My String | The string value to set on each item's myString field. Users can enter any text here. |
Output
The output consists of the same array of items received as input, but each item’s JSON data will have its myString property set or overwritten with the value provided in the node’s input property.
Output structure example (for one item):
{
"json": {
"myString": "User provided string value",
// ... 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
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 may occur if the node parameter
myStringis missing or invalid, but since it defaults to an empty string, this is unlikely.
- 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 during execution on a particular item, and the node is configured to continue on failure, the error details will be attached to that item’s output under an
errorproperty. - Otherwise, the node will throw an error indicating which item caused the failure.
- If an error occurs during execution on a particular item, and the node is configured to continue on failure, the error details will be attached to that item’s output under an