Connects Slack to a Dify agent for thread replies (optionally posting the first reply to the channel) and direct messages, with mrkdwn formatting, thread/DM conversation history and user list, configurable context scope, and optional usage channel restriction.
Version: 0.0.4
Type: extension
Connects Slack to a Dify chat app: reply within Slack threads and to direct messages sent straight to the bot, with conversation history, user info, file uploads, and formatting handled for you.
[!NOTE]
The app also receives and as inputs. These are for advanced use cases - e.g. a linked plugin posting follow-up messages to a specific channel or thread - and most setups won't need them.
To install this plugin, specify the following GitHub repository when selecting "Install Plugin":
https://github.com/fr3on/slack-support-agent
Follow the same setup procedure as the official SlackBot plugin, but with this plugin's scopes and events.
Bot token scopes:
Subscribe to bot events:
Subscribe only under "Subscribe to bot events". Do not add or under "Subscribe to events on behalf of users": those deliver the installing user's private DMs with other people, which are not conversations with the bot. The plugin ignores DMs that Slack didn't deliver under the bot's own authorization as a safeguard, but removing the user-level events keeps that data from being sent to the plugin at all. If you turn on Exclude User-to-User Messages, / are no longer needed (channel context then comes from @mentions and the first thread fetch), and can be removed to stop human channel chatter reaching the plugin.
The / events feed a caching layer that keeps thread context available without repeatedly hitting Slack's thread-history endpoint, which is rate-limited to about 1 request per minute.
For details on setting up the official SlackBot plugin, see:
https://github.com/langgenius/dify-official-plugins/blob/main/extensions/slack_bot/README.md
In the start node of the chat flow app you link to this plugin, add these input fields to receive Slack context:
Example prompt (LLM node in the chat flow app):
Every outbound call builds its address at runtime, so no host can be listed.
Last checked 09/26/2026 01:46 AM · version 0.0.4