Overview
Previously, the HTTP Trigger, Computation, HTTP Request, and Plugin nodes only supported single-line output. Any line breaks in the original content were automatically replaced with spaces.
With this update, these nodes now support multi-line output, preserving line break formatting in most scenarios.
Affected Nodes
HTTP Trigger Node
Computation Node
HTTP Request Node
Plugin Node
Typical Cases
Text concatenated in a Computation Node contains line breaks, and you want them displayed as-is in subsequent nodes.
API data returned by a Plugin or HTTP Request contains a multi-line structure, and you want it fully preserved.
Multi-line Output Rules
Output scenarios:
Output to a multi-line field: line breaks are preserved.
Output to a single-line field: line breaks are replaced with spaces.
Condition-setting scenarios:
Conditions against a multi-line field: line breaks are preserved.
Conditions against a single-line field:
As the comparison value (right-hand side): line breaks are replaced with spaces.
As the field value (left-hand side): line breaks are preserved.
Note: Assigning node output to a "Single-line" form field will still replace line breaks with spaces, since single-line fields do not support line breaks.
Optimization Details
The following scenarios show how the updated behavior improves on the previous version.
1. Writing to Multi-line Fields / Using as Comparison Values (Right-hand Side)
When a node outputs multi-line text and you use it in Add/Update/Delete/Query/Add Path nodes—either to fill a “Multi-line” field or as a filter value (right-hand side):
| Before | After |
Original | Hello\nJohn | Hello\nJohn |
Write Result | Hello John (line break lost) | Hello\nJohn (line break preserved) |
Write the result to a multi-line field in the specified form—the line breaks will be preserved when displayed.
2. Condition Matching: Multi-line Field as the Compared Object (Left-hand Side)
When node output is used in a Conditional Branch node as the compared value (left-hand side), with the match condition set to equals or equals any of:
| Before | After |
Original | Hello\nJohn | Hello\nJohn |
Node Output | Hello John | Hello\nJohn |
Match Target | Hello\nJohn | Hello\nJohn |
Match Result | ❌ Not equal (line break replaced with space) | ✅ Equal (line break preserved, exact match) |
For example, a Conditional Path node filters on a multi-line field:
Line breaks in the left-hand side value are no longer replaced with spaces, making condition matching more accurate.
Important Notes
💡 The following may affect a small number of users. Please review accordingly.
If you previously worked around the line break matching issue by changing the match value (right-hand side) from multi-line text to single-line text with spaces (e.g., Hello\nJohn → Hello John), please revert it back to multi-line text. Otherwise, the condition will no longer match correctly.