langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Enhancement Request for "User Input" Node in Chatflow #20349

New Issue
Closed
opened 2026-02-21 20:06:58 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 20:06:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @yanpx169 on GitHub (Nov 16, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Feature Request: User Input Node for Enhanced Workflow Interaction

  1. Problem Statement
    Currently, when deploying multiple applications with different functionalities, users are provided with separate entry points (URLs) for each application. This fragmented experience requires users to locate the correct URL for each use case, leading to inconvenience and reduced usability. To streamline the process, we aim to provide a unified entry point and handle diverse requests within a single workflow. For ambiguous or unclear cases, we propose a User Input Node to pause execution, interact with users to clarify inputs, and resume processing upon confirmation.

  2. Node Overview
    The User Input Node is designed to temporarily suspend workflow execution, allowing manual intervention to adjust or confirm parameters. It works in conjunction with intermediate output nodes to support dynamic workflow routing (e.g., confirming a user’s intent before proceeding to specific branches).

Key Use Cases:
• Clarifying ambiguous user requests.

• Collecting additional input during workflow execution.

• Re-routing workflows based on real-time user feedback.

Limitations:
• A maximum of 5 User Input Nodes per loop cycle.

• The node awaits user input for a 5-minute timeout; if no response is received, the workflow terminates or follows a fallback path.

  1. Parameter Configuration
    The node supports the following parameter settings:

3.1 Default Values
• Allow referencing outputs from previous nodes as default values (via variable interpolation, e.g., {{input}}).

3.2 Validation Rules
• Required/Optional: Mark parameters as mandatory or optional.

• Numerical Range: Define min/max values for number inputs.

• Text Length: Set maximum/minimum character counts for text inputs.

• Additional Rules: Consistent with validation rules supported by the Start Node (e.g., regex patterns, custom validation scripts).

  1. Example Usage
    A workflow integrates a User Input Node after an initial AI-based classification step. If the classification confidence is low, the workflow pauses and prompts the user:
    “Did you mean to [Option A] or [Option B]? Please confirm.”

The user’s selection then determines the subsequent branch (e.g., A → Route X, B → Route Y).

  1. Acceptance Criteria
    The node pauses execution and waits for user input for up to 5 minutes.

Default values can be dynamically populated from previous node outputs.

All validation rules (required, numerical, text length) are enforced.

The node integrates seamlessly with loop logic (max 5 nodes/cycle).

Timeout handling follows graceful fallback behavior.

  1. Additional Notes
    • This node should be compatible with Dify’s existing variable system and loop controls.

• The UI should clearly indicate when a workflow is awaiting user input.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @yanpx169 on GitHub (Nov 16, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Feature Request: User Input Node for Enhanced Workflow Interaction 1. Problem Statement Currently, when deploying multiple applications with different functionalities, users are provided with separate entry points (URLs) for each application. This fragmented experience requires users to locate the correct URL for each use case, leading to inconvenience and reduced usability. To streamline the process, we aim to provide a unified entry point and handle diverse requests within a single workflow. For ambiguous or unclear cases, we propose a User Input Node to pause execution, interact with users to clarify inputs, and resume processing upon confirmation. 2. Node Overview The User Input Node is designed to temporarily suspend workflow execution, allowing manual intervention to adjust or confirm parameters. It works in conjunction with intermediate output nodes to support dynamic workflow routing (e.g., confirming a user’s intent before proceeding to specific branches). Key Use Cases: • Clarifying ambiguous user requests. • Collecting additional input during workflow execution. • Re-routing workflows based on real-time user feedback. Limitations: • A maximum of 5 User Input Nodes per loop cycle. • The node awaits user input for a 5-minute timeout; if no response is received, the workflow terminates or follows a fallback path. 3. Parameter Configuration The node supports the following parameter settings: 3.1 Default Values • Allow referencing outputs from previous nodes as default values (via variable interpolation, e.g., {{input}}). 3.2 Validation Rules • Required/Optional: Mark parameters as mandatory or optional. • Numerical Range: Define min/max values for number inputs. • Text Length: Set maximum/minimum character counts for text inputs. • Additional Rules: Consistent with validation rules supported by the Start Node (e.g., regex patterns, custom validation scripts). 4. Example Usage A workflow integrates a User Input Node after an initial AI-based classification step. If the classification confidence is low, the workflow pauses and prompts the user: “Did you mean to [Option A] or [Option B]? Please confirm.” The user’s selection then determines the subsequent branch (e.g., A → Route X, B → Route Y). 5. Acceptance Criteria The node pauses execution and waits for user input for up to 5 minutes. Default values can be dynamically populated from previous node outputs. All validation rules (required, numerical, text length) are enforced. The node integrates seamlessly with loop logic (max 5 nodes/cycle). Timeout handling follows graceful fallback behavior. 6. Additional Notes • This node should be compatible with Dify’s existing variable system and loop controls. • The UI should clearly indicate when a workflow is awaiting user input. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement🌊 feat:workflow labels 2026-02-21 20:06:58 -05:00
yindo closed this issue 2026-02-21 20:06:58 -05:00
yindo commented 2026-02-21 20:06:58 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 18, 2025):

Hi, @yanpx169. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You proposed a "User Input" node for chatflows to pause execution and gather user input.
  • Features suggested include parameter validation, default values, a 5-minute timeout, and a limit of 5 nodes per loop cycle.
  • The goal is to enhance workflow flexibility and user experience with real-time interaction and dynamic routing.
  • There has been no further activity or comments on this proposal.

Next Steps:

  • Please let me know if this feature is still relevant to the latest version of Dify by commenting on this issue.
  • If I do not hear back within 15 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 18, 2025): Hi, @yanpx169. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You proposed a "User Input" node for chatflows to pause execution and gather user input. - Features suggested include parameter validation, default values, a 5-minute timeout, and a limit of 5 nodes per loop cycle. - The goal is to enhance workflow flexibility and user experience with real-time interaction and dynamic routing. - There has been no further activity or comments on this proposal. **Next Steps:** - Please let me know if this feature is still relevant to the latest version of Dify by commenting on this issue. - If I do not hear back within 15 days, I will automatically close this issue. Thank you for your understanding and contribution!
yindo commented 2026-02-21 20:06:59 -05:00
Author
Owner
Copy Link
Copy Source

@yanpx169 commented on GitHub (Dec 22, 2025):

This feature is still available in the latest version of Dify. The latest version of Dify still does not have this feature.

@yanpx169 commented on GitHub (Dec 22, 2025): This feature is still available in the latest version of Dify. The latest version of Dify still does not have this feature.
yindo commented 2026-02-21 20:06:59 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 22, 2025):

@crazywoola The user confirmed that the "User Input" node feature is still relevant and missing in the latest version of Dify. Could you please assist with this issue?

@dosubot[bot] commented on GitHub (Dec 22, 2025): @crazywoola The user confirmed that the "User Input" node feature is still relevant and missing in the latest version of Dify. Could you please assist with this issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🌊 feat:workflow 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#20349
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?