Overview
The node, named "Template String Node," is designed to handle and manipulate multi-line text content for use in subsequent nodes within an n8n workflow. It essentially passes through the input data's content field unchanged, making it useful as a placeholder or simple transformer when you want to ensure that multi-line text or JSON content is carried forward without modification.
Practical examples include:
- Preparing or standardizing multi-line text messages before sending them to other services.
- Passing JSON content stored in the input to downstream nodes without alteration.
- Serving as a base node for further customization or extension in workflows involving text manipulation.
Properties
| Name | Meaning |
|---|---|
| Content | A required multi-line string input where users can enter plain text content. |
| Content (JSON) | An optional JSON input allowing users to provide structured JSON content instead of text. |
Output
The node outputs an array of items where each item contains a json object with a single property:
content: This holds the value of thecontentfield from the input data, passed through exactly as received.
No binary data output is produced by this node.
Example output structure:
[
{
"json": {
"content": "multi line text here"
}
}
]
Dependencies
This node does not require any external services, API keys, or special environment variables. It operates purely on the input data provided within the workflow.
Troubleshooting
- Empty or missing content: Since the
contentproperty is required, ensure that the input data includes this field; otherwise, the node will pass undefined or empty values downstream. - Incorrect data type: If the input
contentis not a string or valid JSON (depending on which property is used), downstream nodes expecting specific formats may fail. - No transformation applied: Users expecting the node to modify or template the content should note that this node currently only passes the content through unchanged.