langgenius/dify-docs
1
0
Fork 0
mirror of https://github.com/langgenius/dify-docs.git synced 2026-07-22 04:15:24 -04:00
Code Issues 10 Packages Projects Releases Wiki Activity

modify based on feedback

Browse Source
This commit is contained in:
Riskey
2026-01-28 21:40:53 +08:00
parent 47571f560b
commit 1f25e0384b
1 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
en/use-dify/nodes/human-input.mdx
+12 -12
View File
@@ -40,29 +40,29 @@ Choose the channel through which the request is delivered. Currently available m
Customize what appears in the request form:
- Format and structure the content using **Markdown** syntax
- **Format and structure with Markdown**
- Reference available **variables** to display dynamic data
Use headings, lists, bold text, links, and other Markdown elements to present information clearly.
- **Display dynamic data with variables**
Reference workflow variables to show dynamic content, such as AI-generated text for review or any needed contextual information from upstream nodes.
<Tip>
If you reference the `text` output variable from a reasoning model, the form will display the model's thinking process along with the final answer.
If you reference the `text` output variable from a reasoning model, the form will display the model's thinking process along with the final answer.
To show only the answer, toggle on **Enable Reasoning Tag Separation** for the corresponding LLM node.
</Tip>
- Add interactive **input fields** where recipients can provide input or make edits
- **Collect input with input fields**
<Info>
Input fields can be pre-filled with variables or static content that recipients can edit.
Each input field becomes an output variable for use in downstream nodes.
</Info>
Input fields can start empty or pre-filled with variables (e.g., LLM output to refine) or static text (e.g., example or default values) that recipients can edit.
Each input field becomes a variable for downstream use. For instance, pass edited content for further processing or send feedback to an LLM for regeneration.
### User Action
Define the decision buttons that recipients can click.
Each button creates a corresponding branch from the Human Input node, routing execution based on the decision made.
Define the decision buttons that recipients can click. Each button routes the workflow to a different execution path.
For example, a `Post` branch might lead to nodes that trigger content publishing, while a `Regenerate` branch might loop back to an LLM node to revise the content.