mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
[Enhancement]: Socket suppport for Slack Trigger #807
Reference in New Issue
Block a user
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?
Originally created by @yt-koike on GitHub (Nov 16, 2025).
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Dify 1.10 finally has got a trigger feature I've always wanted. I tried that feature but realized that Slack Trigger supports callback URL but not Socket mode of slack. As I use self-hosed Dify and am reluctant to expose an external endpoint, I'd appreciate it if there's a support for socket mode on Slack Trigger.
Thank you.
2. Additional context or comments
No response
3. Can you help us with this feature?
@yt-koike commented on GitHub (Nov 16, 2025):
I'm not quite familiar with how to develop a trigger plugin for Dify but I'm very keen to contribute to this issue!
@kurokobo commented on GitHub (Nov 16, 2025):
@yt-koike
For reference, I’d like to share my understanding.
This isn’t limited to the Slack plugin, but currently, the trigger feature is implemented based on webhooks. It’s designed and built on the premise that external SaaS will push events to Dify via HTTP.
Also, in the cloud version of Dify, plugins run as AWS Lambdas, so the architecture fundamentally doesn’t allow for any kind of persistent process. Because of this, it’s difficult—at least in the cloud version—to have a client within a plugin that maintains a constant connection to external SaaS.
(Of course, I’m hoping that the trigger feature will be enhanced and that this kind of architecture will eventually be natively supported.)
As for self-hosted environments, it might be technically possible to create a plugin that, for example, receives events via WebSocket and then POSTs them to its own callback URL. Still, this would be a bit of a tricky implementation, and I’m not sure if the Dify team would accept plugins that only work outside the cloud version.
Hope this helps.
@yt-koike commented on GitHub (Nov 16, 2025):
@kurokobo Thank you very much for your information!
OK, I think I understand that WebSocket support for trigger features are not so friendly for cloud users and process managing so I will take a different approach.
I will try to develop a simple Python script which receives events via WebSocket and redirects to Dify. The program would be very simple because Dify 1.10 can process incoming events.
This approach is for general purpose usages, not only for Slack. If it succeeded, I would try that to connect Discord to Dify too.
With that, I'm closing this issue. Thank you.