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 20:29:14 +08:00
committed by GitHub
parent ca9a126021
commit e9e244d4b3
1 changed files with 10 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
en/use-dify/nodes/agent.mdx
+10 -8
View File
@@ -1,21 +1,23 @@
### Form Content
Customize what appears in the request form:
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.
For example, reference an LLM node's output to show AI-generated content that recipients can review.
- **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.
<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** to collect information from recipients.
- **Collect input with input fields**
Input fields can be pre-filled with variables (to show suggested content) or static text (to provide examples or default values). Recipients can edit the pre-filled content or leave it unchanged.
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.
Each input field becomes an variable that can be referenced in downstream nodes to incorporate recipient input. For example, pass edited content to a publishing node or send feedback to an LLM node for regeneration.
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.