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

test

Browse Source
This commit is contained in:
Riskey
2026-01-28 21:27:08 +08:00
committed by GitHub
parent e9e244d4b3
commit 41fc436498
1 changed files with 16 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
en/use-dify/nodes/agent.mdx
+16 -4
View File
@@ -1,6 +1,6 @@
### Form Content
Customize what appears in the request form.
Customize what appears in the request form:
- **Format and structure with Markdown**
@@ -8,7 +8,7 @@ Customize what appears in the request form.
- **Display dynamic data with variables**
Reference an LLM node's output that recipients can review, or provide any workflow data as context for more informed decisions.
Reference workflow variables to show dynamic content, such as AI-generated text for review or any contextual information that informs recipient decisions.
<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.
@@ -18,6 +18,18 @@ Customize what appears in the request form.
- **Collect input with input fields**
Input fields can be empty, or pre-filled with variables (e.g., AI-generated text to refine) or static text (e.g., example responses or default values) that recipients can edit.
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 an variable that downstream nodes can reference. For example, pass edited content to a publishing node or send feedback to an LLM node for regeneration.
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 corresponds to a separate execution branch.
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.
<Tip>
Use preset button styles to visually distinguish actions.
For example, use a prominent style for key actions like `Approve` and a subtler one for secondary options.
</Tip>