Node Function
The Text Collection Node belongs to the Information Collection Node, used to collect text information at a specific stage in the workflow. When the workflow proceeds to the "Text Collection Node", the system will display the developer's preset guidance to users. At this point, the text entered by users will automatically proceed to the workflow and be undertaken by the string type "Text" field. The follow-up workflow can use this field to acquire user-entered text information.
Directions
Input Variables
Input variables take effect only within the same node and cannot be used cross-node. Support up to 50 input variables to meet multi-input scene required. Click Add and configure as follows to add input variables.
|
Variable Name | The variable name can only contain letters, digits, or underscores, must start with a letter or underscore. Required. |
Description | Description of this variable. Optional |
Data source | The data source of this variable supports two options: "refer" and "input". "Refer" allows selecting output variables from all preceding nodes, while "input" supports manually filling in a fixed value. Required |
Type | The data type of this variable is unselectable, defaulting to the variable type of "refer" or the string type of "input". |
Guide words
Support guidance in text collection to ask or prompt user. The prompt input box supports referencing the node's input variable by entering "/".
Note:
The Text Collection Node belongs to the single-round interactive information collection node and will not trigger a rollback operation. During workflow operation, user input will be converted to text format. If the user uploads images or document resources, the system will automatically record and store them in the form of resource URLs.
Output Variable
The node contains two output variables: the text information collected by the node and runtime Error info (data type: object, this field is empty during normal operation). Manual addition is not supported.
Difference between Text Collection Node and Parameter Extraction Node
The Text Collection Node and Parameter Extraction Node both extract information from user input, encapsulate it as output variables, and transfer it to subsequent nodes. They are suitable for business scenarios that collect various data from the user end. However, the two have certain differences in feature positioning, as follows:
|
Interaction Mode | Show guidance and collect user input | Show guidance and prompt the user to enter the parameter information to be extracted. If parameters are missing, trigger a follow-up question to guide the user to provide the required information. |
Core Features | Write the user answer as-is without any parsing | Extract specific content from user input, focus on "key information" |
Output Format | User input is directly encapsulated as a "Text" variable of string type and retained as-is. | Parse user input and map it to preset parameter fields to output structured parameter data |
Applicable Scenarios | Collect feedback, retain user statements for compliance, and transmit original information to node processing. | Extract specific parameters (such as name and mobile number) from user input, guide users through multiple rounds to complement information, and other scenarios. |
rollback mechanism | No support for rollback, no follow-up question mechanism | When the target parameter cannot be extracted, multiple rounds of rollback will be performed. You can re-enter this parameter value in the subsequent process and modify it. |
Node Example
In the school "Course Quality Assessment" workflow, when the process advances to the "Student Feedback Collection" step, insert text collection nodes as follows:
The complete workflow configuration is as follows:
The running results are as follows: