OUT-1985 | OUT-2058 | Support companyIds in webhook event Notifications - #889
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
companyIds in webhook event Notifications
arpandhakal
approved these changes
Jul 23, 2025
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.
Changes
companyIdswith new notification create fields in Webhook eventsTesting Criteria:
client.created- Create client with companyScreen.Recording.2025-07-23.at.16.04.48.mov
client.updated- Assign one / multiple companiesNOTE: The copilot multi-companies notifications are very buggy. Sometimes the notification chip disappears entirely for no reason.
Screen.Recording.2025-07-23.at.16.12.53.mov
client.updated- unassign companiesScreen.Recording.2025-07-23.at.16.17.06.mov
The count cannot be verified from the UI since access to the company is revoked, if if this company is reassigned, the notification count start again from 0, due to the calls to
markNotificationAsReadwhen companies are unassigned.client.deletedNo changes