v1.10.0-rc1
#27670
Replies: 1 comment
-
|
什么时候发布稳定版本嘞 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Introduce Trigger Funtionality
Trigger = When something → then do something
This is the foundation for event-driven Workflow capabilities, covering the following types:
All of those features are only designed for Workflow, Chatflow / Agent / BasicChat are not supported.
Design Premise
After careful consideration, we concluded that the start node design cannot fully embody the philosophy behind Triggers.
Therefore, we have redesigned the start node as a component bound to WebApp or Service API.
This means:
$current_timeparameter.As a result, we introduced 3 kinds of start nodes, they are all the trigger nodes, and we've already completed the product design, and the UI/UX design is also finished.
The implementation of Trigger will be divided into:
Why
Currently, if you want to build something like a Discord ticket bot → Linear in an enterprise setup, you need custom glue code, pre-published extensions, and manual token retrieval from the Discord developer console instead of simple one-click OAuth binding.
Similar pain points exist for GitHub PR plugin review, Hello Dify email replies, etc., all requiring manual download/upload/trigger actions.
While it’s possible to achieve similar outcomes using external automation platforms with Dify API calls, the cross-platform experience is fragmented, and many external automation platforms are adding their own LLM orchestration capabilities.
Developers often have to host multiple services to poll for events. Endpoints can help, but they are not purpose-built for trigger scenarios, making the configuration flow unintuitive.
Multiple community members have requested this feature:
What's Changed
toolCredentialToFormSchemasby @jingfelix in fix: add missing toType totoolCredentialToFormSchemas#26681anyusages and strengthen typings across web and base by @ZeroZ-lab in refactor(types): removeanyusages and strengthen typings across web and base #26677convert_stream_simple_responseby @hyongtao-code in Fix: avoid duplicate response_chunk update inconvert_stream_simple_response#26965/workflows/draftAPI due to stale closure values #27612) by @issac2e in fix: resolve stale closure values in LLM node callbacks (#27612) #27614New Contributors
Full Changelog: 1.9.1...1.10.0-rc1
This discussion was created from the release v1.10.0-rc1.
Beta Was this translation helpful? Give feedback.
All reactions