Creator Center
/Extension/Slack Support Agent
app icon

Slack Support Agent

Verified by Dify
No ratings yet
0
F
fr3on/slack-support-agent

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.

ProductivitySocial

Slack Support Agent

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.

Contents

  • Features
  • Settings
  • Install
  • Setup
  • Usage in your Dify app
  • Support

Features

  • Threads - reply within Slack threads, with an optional setting to also post the first reply to the channel
  • Direct messages - reply to DMs sent straight to the bot, with the conversation continuing turn-to-turn just like Dify's own chat UI, not just @mentions in channels
  • File uploads - Slack file attachments are downloaded and passed to the linked app automatically
  • formatting - the app's Markdown answer is converted to Slack's and split across multiple messages if it exceeds Slack's block text limit
  • Context, your way - the linked app receives thread/DM conversation history and a resolved user list; how much history it gets is configurable (see Settings)
  • Channel restriction - optionally lock the bot to a single Slack channel

[!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.

Settings

SettingRequiredDescription
AppYesThe Dify chat app that answers Slack messages.
Bot TokenYesYour Slack bot's token.
Allowed ChannelNoRestrict the bot to one channel, in format. Leave blank to allow all channels. Doesn't apply to DMs.
Thread Context Sent to AppNoHow much thread history to send with each reply: Full thread (default), Root message only, or Message right before the mention.
Exclude User-to-User MessagesNoWhen on, messages people send to each other in a thread are kept away from the linked app: it only receives the thread's root message, the agent's own replies, and messages that @mention the agent (DMs are unaffected, since they are always with the agent). Those messages are also no longer cached. Default: off (the full thread is sent).
Summarize Thread HistoryNoCondense the selected thread history into a single AI-generated summary before sending it, instead of the raw message list. Short conversations are sent as-is with no extra cost.
Summarization ModelNoWhich model to use for the above. Leave blank to use Dify's default system reasoning model; pick a specific model for explicit control over cost/quality.
Broadcast First ReplyNoAlso post the bot's first reply in a thread to the channel itself, not just the thread.
Allow RetryNoProcess Slack's automatic retries of a webhook delivery instead of ignoring them. Off by default to avoid duplicate replies.
Skip App Timeout Error NotificationsNoIf the linked app times out, stay silent instead of posting an error message to Slack.

Install

To install this plugin, specify the following GitHub repository when selecting "Install Plugin":

https://github.com/fr3on/slack-support-agent

Setup

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:

EventPurpose
Reply when someone @-mentions the bot in a channel
Reply to direct messages sent to the bot
Cache messages in public channel threads
Cache messages in private channel threads

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

Usage in your Dify app

In the start node of the chat flow app you link to this plugin, add these input fields to receive Slack context:

Input fieldField type
Paragraph, max length e.g. 65535
Paragraph, max length e.g. 65535
File List
Short Text, max length e.g. 48
Short Text, max length e.g. 48

Example prompt (LLM node in the chat flow app):

Support

  • Source repository: https://github.com/fr3on/slack-support-agent
  • Issues / questions: https://github.com/fr3on/slack-support-agent/issues
  • Contact: @fr3on on GitHub
CATEGORY
Extension
VERSION
0.0.4
fr3on·Updated a month ago
REPOSITORY
https://github.com/fr3on/slack-support-agent
REQUIREMENTS
LLM invocation
Tool invocation
App invocation
Endpoint registration
Maximum memory
512MB
Maximum storage
1MB
Access domain

Every outbound call builds its address at runtime, so no host can be listed.

Security
Security Rating

Last checked 09/26/2026 01:46 AM · version 0.0.4

Give a rate
SHARE WITH