Example Node

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 where this node is useful include:

• Adding a constant or user-defined string value to all items passing through a workflow.
• Overwriting or initializing a specific field in each item with a fixed string.
• Simple data enrichment or tagging of items before further processing.

For example, if you want to tag all incoming records with a status label like "Processed" or add a note to each item, this node can be configured to do so by setting the "My String" property accordingly.

Properties

Output

The node outputs the same number of items as it receives, with each item’s JSON data modified to include or update the myString property with the user-provided string.

Output structure example for one item:

{
  "myString": "User provided string",
  // ... other original fields remain unchanged
}

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

• Empty or missing "My String" value: If the "My String" property is left empty, the node will set the myString field to an empty string, which might not be intended. Ensure to provide a meaningful string.
• Errors during execution: If an error occurs while processing an item, the node supports continuing on failure if enabled; otherwise, it will throw an error indicating the item index causing the issue.
• Data type assumptions: The node assumes input data items have a JSON structure. Non-JSON inputs may cause unexpected behavior.

Links and References

• n8n Documentation - Creating Custom Nodes
• n8n Workflow Data Structure