Overview
This node, named "Example Node," is a basic transformation node designed to add or overwrite a string property in each input item. It takes an input string from the user and sets this string as the value of the myString field in the JSON data of every incoming item.
Common scenarios where this node is useful include:
- Adding a constant label or tag to all items passing through a workflow.
- Overwriting or setting a specific string property uniformly across multiple data items.
- Simple data enrichment or annotation before further processing.
For example, if you want to mark all incoming records with a status like "Processed" or add a note such as "Reviewed by QA", this node can do that easily by setting the myString property accordingly.
Properties
| Name | Meaning |
|---|---|
| My String | The string value to set on each item's myString field. This value will be added or overwrite the existing one. |
Output
The output consists of the same number of items as the input. Each item's JSON data will have a new or updated property called myString containing the string provided via the input property.
No binary data is produced by this node.
Example output JSON for one item:
{
"myString": "Your input string here"
}
Dependencies
- No external services or API keys are required.
- This node operates purely on the input data within the workflow.
Troubleshooting
- If the node throws an error, it may be due to invalid input data or issues retrieving the input parameter.
- When "Continue On Fail" is enabled, errors on individual items will not stop execution; instead, error details will be attached to the corresponding item.
- Common error messages relate to parameter retrieval failures or unexpected input data formats.
- To resolve errors, ensure the input data is valid and the "My String" property is correctly configured.