docs(email): document replaceToRecipient override fixes NV-7732#1104
Merged
Conversation
Co-authored-by: dima <dima@novu.co>
✅ Deploy Preview for docs-novu ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jainpawan21
approved these changes
May 21, 2026
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.
Docs sync — Providers / Integrations (auto-generated draft)
This PR brings the Providers / Integrations docs in line with changes merged into
novuhq/novubetween 2026-05-14 and 2026-05-21.
Changes covered
/platform/integrations/email— documentedreplaceToRecipientin the sending email overrides list and clarified default merge vs replace behavior in the callout.toaddress instead of only merging override recipients.Reviewed, no change needed
contextKeyson inbox channel connection/endpoint routes (security fix); platform inbox docs do not document caller-suppliedcontextKeysquery params for those routes.credentials: {}for API-key callers instead of omitting the field; behavior for callers is unchanged (no secrets exposed).GET /v2/subscribers/:id/preferences; no API contract change.Big WIP products spotted (not drafted here — flagging for the team)
/agents/public.Conventions followed
/platform/integrations/email/index.mdx.<Callout>for behavioral notes alongside the override field list.🤖 Generated by docs-sync automation. Open as draft — please review for accuracy before marking ready.
Linear: NV-7732