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 for this node include:
- Adding a static or user-defined string to all items passing through a workflow.
- Overwriting or initializing a specific field with a constant value.
- Simple data enrichment where a fixed label or note needs to be attached to each item.
For example, if you want to tag all records with a status message or a category name, you can use this node to set that string uniformly.
Properties
| Name | Meaning |
|---|---|
| My String | The string value to assign to the myString field in each item's JSON data. This can be any text entered by the user. |
Output
The output consists of the same number of items as the input, with each item’s JSON data modified to include or update the myString property with the user-provided string.
Output structure example (JSON part):
{
"myString": "User provided string"
}
No binary data is produced by this node.
Dependencies
- No external services or API keys are required.
- The node operates purely on the input data within the workflow.
Troubleshooting
- Error Handling: If an error occurs while processing an item, the node either continues processing subsequent items (if configured to continue on failure) or throws an error that includes the index of the failed item.
- Common Issues:
- Providing invalid input data types (non-array inputs) may cause unexpected behavior.
- Forgetting to provide a string value for the "My String" property will result in empty strings being assigned.
- Error Messages:
- Errors thrown during execution will indicate the item index causing the problem, helping to identify problematic data.