feat: allow botkube to react to messages from other bots/workflows #1491
+2
−2
Conversation
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
Author
|
@pkosiec 👀 |
nthtrung09it
suggested changes
Jan 30, 2026
nthtrung09it
left a comment
nthtrung09it
left a comment
There was a problem hiding this comment.
Bug: b.botID is set from authResp.UserID (a User ID, U-prefixed) at slack_socket.go:86, while ev.BotID from AppMentionEvent is a Bot ID (B-prefixed). These are different Slack ID namespaces, so the comparison ev.BotID == b.botID will never match.
This means the bot will never filter its own messages, which could cause infinite loops if bot replies trigger AppMentionEvent.
Fix: Use ev.User == b.botID instead of ev.BotID == b.botID to correctly compare User IDs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Changed Botkube behavior so it can be triggered by other bots/workflows in Slack, which is a feature that used to work in the past.
A common use case is a Slack workflow that runs on a given schedule. E.g. to invoke botkube for knowing the current scale of nodes/pods every morning at 10:30 AM.
Testing
For testing this functionality, it is needed to create a local k8s cluster (In my case I used K3D), build and run the code by using the steps mentioned in the contribuiting guidelines, and set up a Slack workflow.
Related issue(s)
Resolves #1360