docs: Document Notification Payload Schema (#79)#92
Merged
Abd-Standard merged 1 commit intoJun 19, 2026
Merged
Conversation
Adds NOTIFICATION_PAYLOAD_SCHEMA.md documenting the full structure, required/optional fields, validation rules, and JSON examples for all four notification channels (Discord, email, webhook, SMS). Closes Core-Foundry#79 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
Adds
NOTIFICATION_PAYLOAD_SCHEMA.mdas requested in #79.What's included
CreateScheduledNotificationInput— all required and optional fields with types, defaults, and constraintstargetRecipientformat per channeleventIdprevents duplicate deliveriesThe schema is derived directly from the existing TypeScript interfaces in
listener/src/types/scheduled-notification.tsand the REST API inlistener/src/api/events-server.ts, so it accurately reflects the implementation.Closes #79