Repository navigation
feat: add the user_connection and user_connection_status_requested event models - #1660
Merged
WilliamBergamin merged 2 commits intoOct 22, 2026
Merged
Conversation
Slack sends this event when it has no connection status for a user, and apps answer with apps.user.connection.update. The model lets Bolt apps register app.event(UserConnectionStatusRequestedEvent.class, ...).
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1660 +/- ##
=======================================
Coverage ? 72.98%
Complexity ? 4630
=======================================
Files ? 486
Lines ? 14632
Branches ? 1524
=======================================
Hits ? 10679
Misses ? 3049
Partials ? 904
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
Add UserConnectionEvent with its handler and payload, so Bolt apps can register app.event(UserConnectionEvent.class, ...) for both the connect and disconnect subtypes. The subtype stays unset by default so Bolt keys the listener on the type alone, like EmojiChangedEvent. Also add event_ts to UserConnectionStatusRequestedEvent to match node-slack-sdk#2783. Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
WilliamBergamin
marked this pull request as ready for review
October 22, 2026 20:52
zimeg
approved these changes
Oct 22, 2026
zimeg
left a comment
Member
There was a problem hiding this comment.
☕ @WilliamBergamin LGTM! It's exciting for what this unlocks 🔏
WilliamBergamin
deleted the
feat-user-connection-status-requested-event
branch
October 22, 2026 20:58
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.
This pull request adds the
user_connectionanduser_connection_status_requestedevent models, so Bolt apps can registerapp.event(UserConnectionEvent.class, ...)andapp.event(UserConnectionStatusRequestedEvent.class, ...).UserConnectionEventin slack-api-model, plus its handler and payload in slack-app-backend. One class covers both theconnectanddisconnectsubtypes:trigger_idis set onconnect, andenterprise_idcan be set ondisconnect. The subtype stays unset by default so Bolt keys the listener on the type alone, likeEmojiChangedEvent.UserConnectionStatusRequestedEventin slack-api-model, plus its handler and payload in slack-app-backend, followingEntityDetailsRequestedEvent.Testing
From an app with
features.user_connectionsenabled and subscribed to both events:Category (place an
xin each of the[ ])Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you agree to those rules.
🤖 Generated with Claude Code