langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #4067] feat: add a new built-in tool of Slack Incoming Webhook #24384

New Issue
Closed
opened 2026-02-21 20:22:54 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:22:54 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/4067

State: closed
Merged: Yes

Description

Add a new built-in tool of Slack Incoming Webhook to send message.

Fixes #4066

Type of Change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

  1. Create a new Agent.
  2. Add a workflow of the new added Slack Incoming Webhook built-in tool.
  3. Create a Slack App in your Slack workspace.
  4. Get Slack Incoming Webhook url from Slack App interface.
  5. Config the webhook url to the built-in tool.
  6. Run the Agent to trigger an invoke of the Slack Incoming Webhook built-in tool.
  7. Got the message in Slack.

Suggested Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
**Original Pull Request:** https://github.com/langgenius/dify/pull/4067 **State:** closed **Merged:** Yes --- # Description Add a new built-in tool of Slack Incoming Webhook to send message. Fixes #4066 ## Type of Change Please delete options that are not relevant. - [x] New feature (non-breaking change which adds functionality) # How Has This Been Tested? 1. Create a new Agent. 2. Add a workflow of the new added Slack Incoming Webhook built-in tool. 3. Create a Slack App in your Slack workspace. 4. Get Slack Incoming Webhook url from Slack App interface. 5. Config the webhook url to the built-in tool. 6. Run the Agent to trigger an invoke of the Slack Incoming Webhook built-in tool. 7. Got the message in Slack. # Suggested Checklist: - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] My changes generate no new warnings
yindo added the pull-request label 2026-02-21 20:22:54 -05:00
yindo closed this issue 2026-02-21 20:22:54 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#24384
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?