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

[☂️] Dify Trigger — Frontend: Plugin Trigger Node & Configuration Panel #16277

New Issue
Closed
opened 2026-02-21 19:25:25 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 19:25:25 -05:00
Owner
Copy Link
Copy Source

Originally created by @lyzno1 on GitHub (Aug 19, 2025).

Originally assigned to: @Yessenia-d on GitHub.

[Sub-issue] Frontend — Plugin Trigger Node & Configuration Panel

Assignee: @Yessenia-d
Related umbrella: #23981

DDL

DDL: 2025.9.15

Goal

Implement the Plugin Trigger Node frontend components including:

  • Canvas node component with plugin display
  • Configuration panel with plugin selector and event configuration
  • Integration with block selector and node system
  • Plugin parameter configuration and validation functionality

This covers the frontend UI for plugin-based workflow triggers, enabling workflows to be triggered by external plugin events.

Scope

  • Plugin trigger node canvas component extending trigger node pattern
  • Configuration panel with plugin selector and event type configuration
  • Dynamic parameter configuration form (similar to tool node pattern)
  • Block selector integration and node registration
  • Form validation and error handling
  • TypeScript types and component structure

Out of Scope

  • Backend plugin event dispatcher implementation
  • Actual plugin execution logic
  • Plugin marketplace or installation features

Technical Notes

  • Follow existing trigger node patterns (schedule/webhook)
  • Leverage tool node's dynamic form configuration approach
  • Integrate with existing plugin system architecture
  • Ensure consistent UX with other trigger types
Originally created by @lyzno1 on GitHub (Aug 19, 2025). Originally assigned to: @Yessenia-d on GitHub. # [Sub-issue] Frontend — Plugin Trigger Node & Configuration Panel **Assignee:** @Yessenia-d **Related umbrella:** #23981 ## DDL **DDL:** 2025.9.15 ## Goal Implement the **Plugin Trigger Node** frontend components including: - Canvas node component with plugin display - Configuration panel with plugin selector and event configuration - Integration with block selector and node system - Plugin parameter configuration and validation functionality > This covers the frontend UI for plugin-based workflow triggers, enabling workflows to be triggered by external plugin events. --- ## Scope - Plugin trigger node canvas component extending trigger node pattern - Configuration panel with plugin selector and event type configuration - Dynamic parameter configuration form (similar to tool node pattern) - Block selector integration and node registration - Form validation and error handling - TypeScript types and component structure ### Out of Scope - Backend plugin event dispatcher implementation - Actual plugin execution logic - Plugin marketplace or installation features ## Technical Notes - Follow existing trigger node patterns (schedule/webhook) - Leverage tool node's dynamic form configuration approach - Integrate with existing plugin system architecture - Ensure consistent UX with other trigger types
yindo added the 🌊 feat:workflow label 2026-02-21 19:25:25 -05:00
yindo closed this issue 2026-02-21 19:25:26 -05:00
yindo commented 2026-02-21 19:25:26 -05:00
Author
Owner
Copy Link
Copy Source

@lyzno1 commented on GitHub (Aug 20, 2025):

@crazywoola please assign me this issue and add all sub issues to milestone.

@lyzno1 commented on GitHub (Aug 20, 2025): @crazywoola please assign me this issue and add all sub issues to milestone.
yindo commented 2026-02-21 19:25:26 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 20, 2025):

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

Issue Summary:

  • You proposed developing frontend components for a Plugin Trigger Node, including a canvas node, configuration panel, and dynamic parameter validation.
  • The focus is on UI integration without backend logic.
  • You requested assignment and milestone inclusion from @crazywoola.
  • The work is intended to follow existing trigger node patterns.
  • The deadline was set for September 15, 2025, but there have been no updates or comments since.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 20, 2025): Hi, @lyzno1. 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 developing frontend components for a Plugin Trigger Node, including a canvas node, configuration panel, and dynamic parameter validation. - The focus is on UI integration without backend logic. - You requested assignment and milestone inclusion from @crazywoola. - The work is intended to follow existing trigger node patterns. - The deadline was set for September 15, 2025, but there have been no updates or comments since. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open. - Otherwise, I will automatically close this issue in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:25:26 -05:00
Author
Owner
Copy Link
Copy Source

@lyzno1 commented on GitHub (Sep 20, 2025):

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

Issue Summary:

  • You proposed developing frontend components for a Plugin Trigger Node, including a canvas node, configuration panel, and dynamic parameter validation.
  • The focus is on UI integration without backend logic.
  • You requested assignment and milestone inclusion from @crazywoola.
  • The work is intended to follow existing trigger node patterns.
  • The deadline was set for September 15, 2025, but there have been no updates or comments since.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

Reservations are required

@lyzno1 commented on GitHub (Sep 20, 2025): > Hi, [@lyzno1](https://github.com/lyzno1). 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 developing frontend components for a Plugin Trigger Node, including a canvas node, configuration panel, and dynamic parameter validation. > * The focus is on UI integration without backend logic. > * You requested assignment and milestone inclusion from [@crazywoola](https://github.com/crazywoola). > * The work is intended to follow existing trigger node patterns. > * The deadline was set for September 15, 2025, but there have been no updates or comments since. > > **Next Steps:** > > * Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open. > * Otherwise, I will automatically close this issue in 15 days. > > Thank you for your understanding and contribution! Reservations are required
yindo commented 2026-02-21 19:25:26 -05:00
Author
Owner
Copy Link
Copy Source

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

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

Issue Summary:

  • You opened this issue to create frontend components for a Plugin Trigger Node, including a canvas node, configuration panel, and dynamic parameter forms with validation.
  • The focus is on UI integration without backend logic.
  • You requested assignment and milestone inclusion from the maintainer.
  • The issue was marked as stale due to inactivity but you confirmed it is still relevant.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of Dify by commenting on this issue.
  • If no further activity occurs, I will automatically close the issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 22, 2025): Hi, @lyzno1. 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 opened this issue to create frontend components for a Plugin Trigger Node, including a canvas node, configuration panel, and dynamic parameter forms with validation. - The focus is on UI integration without backend logic. - You requested assignment and milestone inclusion from the maintainer. - The issue was marked as stale due to inactivity but you confirmed it is still relevant. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of Dify by commenting on this issue. - If no further activity occurs, I will automatically close the issue in 15 days. Thank you for your understanding and contribution!
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
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#16277
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?