Skip to content

[Email Service] Document Email Sending event subscriptions#31828

Open
rpots wants to merge 1 commit into
productionfrom
ruisilva/EMAIL-1930
Open

[Email Service] Document Email Sending event subscriptions#31828
rpots wants to merge 1 commit into
productionfrom
ruisilva/EMAIL-1930

Conversation

@rpots

@rpots rpots commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

Documents Email Sending event subscriptions, a new source for Queues event subscriptions. Customers can subscribe per sending domain — the zone apex or a verified sending subdomain — to receive outbound transactional email lifecycle events on a queue.

  • Add an Event subscriptions page under Email Service > Platform, following the same pattern as the other product event-subscription pages (Workers AI, KV, R2), which render shared partials from Queues.
  • Add an email-sending-events partial documenting the six event types (message.delivered, message.deferred, message.bounced, message.failed, message.rejected, message.complained) with example payloads, and noting that Email Routing events are not published on this source.
  • Register the Email Sending source in the Queues Events & schemas reference so it appears alongside the other sources.

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

Documents Email Sending event subscriptions, a new source for Queues
event subscriptions. Customers can subscribe per sending domain — the
zone apex or a verified sending subdomain — to receive outbound
transactional email lifecycle events on a queue.

- Add an Event subscriptions page under Email Service > Platform,
  following the same pattern as the other product event-subscription
  pages (Workers AI, KV, R2), which render shared partials from Queues.
- Add an email-sending-events partial documenting the six event types
  (message.delivered, message.deferred, message.bounced, message.failed,
  message.rejected, message.complained) with example payloads, and
  noting that Email Routing events are not published on this source.
- Register the Email Sending source in the Queues Events & schemas
  reference so it appears alongside the other sources.
@github-actions github-actions Bot added product:queues Cloudflare Queues: https://developers.cloudflare.com/queues size/m labels Jul 1, 2026
@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
* @cloudflare/product-owners
/src/content/docs/queues/ @elithrar, @jonesphillip, @harshil1712, @mia303, @cloudflare/product-owners
/src/content/partials/queues/ @elithrar, @rita3ko, @irvinebroque, @vy-ton, @cloudflare/product-owners

@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Review

💡 1 suggestion found in commit 5328101.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

No code review issues found.

Conventions

Checks PR title, description, and redirect checklist.

No convention issues found.

Style Guide Review

Suggestions (1)
File Issue
partials/queues/event-subscriptions/email-sending-events.mdx line 171 Oxford comma for three or more items — Line adds "including suppression, validation rejection, or spam rejection" Fix: Add a serial comma before "or": "including suppression, validation rejection, or spam rejection" → "including suppression, validation rejection, or spam rejection"

Redirects

No missing redirect entries found.

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command Description
/review Runs a review now. Incremental if a prior review exists, full if not.
/full-review Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.

@irvinebroque irvinebroque left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome - are we going to have an example to share of what you might do with this?

@mia303

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:queues Cloudflare Queues: https://developers.cloudflare.com/queues size/m

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants