feat: per-thread webhook filtering by chat GUID#780
Open
f1sherman wants to merge 3 commits intoBlueBubblesApp:developmentfrom
Open
feat: per-thread webhook filtering by chat GUID#780f1sherman wants to merge 3 commits intoBlueBubblesApp:developmentfrom
f1sherman wants to merge 3 commits intoBlueBubblesApp:developmentfrom
Conversation
Add optional chatGuids column to Webhook entity so webhooks can be scoped to specific iMessage conversations. The dispatch logic extracts chat GUIDs from event data and filters per-webhook. Webhooks without a chat filter retain current global behavior. Chat-filtered webhooks still receive global/system events that have no chat context. Includes a migration for existing production databases.
Pass the new chatGuids field through ServerRepository CRUD methods, REST API validator/router, and Electron IPC handlers so webhooks can be created and updated with a chat filter from both the API and UI. IPC handlers parse chatGuids from JSON for consistency with the REST API response format.
Add a multi-select chat dropdown to the webhook dialog so users can scope webhooks to specific iMessage conversations. The dropdown shows chat display names (or participant addresses for unnamed chats) and is populated from the existing get-chats IPC handler. The webhooks table shows the filter state as "All Chats" or a chat count.
f1sherman
force-pushed
the
configurable-webhooks-per-thread
branch
from
a22d4a8 to
ca038d7
Compare
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
1 participant
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.
Summary
Allow custom webhooks to be configured for each iMessage conversation.
Context
First of all, this is an excellent project, thank you for building it!
I've been running a few openclaw agents using BlueBubbles with separate iMessage Guids per agent for the communication channel and it has been working flawlessly. However, because all webhook requests go to the same endpoint(s), it makes agent isolation pretty difficult. This change enables users to configure separate webhooks per chat Guid. I would imagine this opens up additional use cases as well.
Test plan
server-update,new-server)chatGuidsparameter - verify round-trip through GET