Add slack-support-agent plugin - #3053
Merged
Merged
Conversation
Member
|
please make sure only one bundled package is submitted |
Member
fr3on
force-pushed
the
add-slack-support-agent
branch
from
September 11, 2026 11:01
762b724 to
0f28b61
Compare
Contributor
Author
|
@crazywoola Done, thanks for the pointer! Removed the source tree and left only the packaged .difypkg in the PR |
…lugin dependency - manifest.yaml: add required repo and contact fields - requirements.txt: bump dify_plugin from 0.2.4 to 0.9.0 (marketplace requires >= 0.9.0)
fr3on
force-pushed
the
add-slack-support-agent
branch
from
September 12, 2026 12:12
38bb37e to
3209101
Compare
crazywoola
approved these changes
Sep 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plugin Submission
Plugin information
Submission type
What changed
Adds Slack Support Agent, a Dify extension plugin that connects Slack to a Dify chat app. It replies within Slack threads (optionally also broadcasting the first reply to the channel) and to direct messages sent straight to the bot, with the DM conversation continuing turn-to-turn across multiple messages just like Dify's own chat UI. It passes thread/DM conversation history, resolved user display names, and uploaded files to the linked app; converts the app's Markdown answer into Slack's
mrkdwnformat (splitting across messages if it exceeds Slack's block text limit); and supports an optional single-channel restriction and a configurable thread-context scope (full thread / root message only / message right before the mention).Risk level
Sends Slack message content to the linked Dify app and processes user-uploaded Slack files. No code/SQL execution, no SSH/filesystem/browser automation, and no arbitrary user-controlled URL fetching (the only external calls are to Slack's own API and Slack's own file-download URLs).
Required checks
.envfiles,.gitdirectories, virtual environments, caches, logs, or IDE files.PRIVACY.md, andmanifest.yamlreferences it.Security and privacy notes
To provide conversation context and avoid Slack's thread-history rate limit, the plugin caches recent Slack thread/DM messages (channel, timestamps, sender ID, text) in Dify's plugin storage for up to 24 hours, and persists a Dify
conversation_idper Slack thread/DM to maintain multi-turn context. No other sensitive capabilities. Documented inPRIVACY.md.Local validation
Packaged with the official Dify plugin CLI (
dify-pluginv0.6.10):dify-plugin plugin package ./slack-support-agent -o ./slack-support-agent-0.0.1.difypkgVerified the resulting archive contains only the 11 runtime files (no
.git, caches, or secrets).Reviewer notes
Not yet tested end-to-end against a live Dify instance (Community Edition or Cloud) with a real Slack workspace connected — only exercised locally against the plugin's own logic (unit tests and a mocked Slack/Dify simulation). Flagging this per the "Required checks" box above.