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 consistent string value or inject a static piece of information into each item for further processing.
Practical examples:
- Adding a fixed label or category name to all incoming records.
- Injecting a constant identifier or note into each data item before sending it downstream.
- 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 set on each item's myString field. |
Output
The node outputs the same number of items as it receives, each with its original JSON data augmented or overwritten by a new property:
json.myString: Contains the string value provided via the "My String" input property.
No binary data output is produced by this node.
Dependencies
- No external services or API keys are required.
- The node relies solely on n8n's internal workflow context and standard node parameter retrieval.
Troubleshooting
Common issues:
- If the input data is empty or not properly formatted, the node will still run but simply add the string to whatever JSON exists.
- Errors during execution typically relate to invalid input data or unexpected exceptions in parameter retrieval.
Error messages:
- If an error occurs on a specific item, and "Continue On Fail" is disabled, the node throws an error indicating the item index.
- If "Continue On Fail" is enabled, the node appends an error object alongside the problematic item, allowing the workflow to continue.