A branded email sent only on the autonomous publishing path, carrying the post title, the target keyword as a chip, the word count, the description, a line confirming the post is in the sitemap and the engines were pinged, and a button to read it. Publishing by hand from the panel does not send it.
Also called: publish notification · blog went out email · new post alert
- 1notifyPostPublished() is called after the status flip and the engine announcement.
- 2The recipient is BLOG_NOTIFY_EMAIL, falling back to the owner address only if that is not set.
- 3The mail is best-effort inside a catch — a mail failure never rolls back a post that is already live.
- 4A missing recipient returns skipped rather than throwing.
Keith asked for it directly, and the code quotes him: "I want to receive an email when the blogs go out. So the moment the blog actually gets published from being scheduled, I want that email." The reasoning that follows explains why this one moment earns an interruption: "This is the one moment the autonomous system does something IRREVERSIBLE in public — a URL appears on the site and the search engines are told about it. Everything else it does… is recoverable in private." The recipient variable is separate for a security reason: OWNER_EMAIL grants platform-owner powers, and "setting it so a notification has somewhere to go would be a privilege change wearing a feature's clothes."
- Autonomous publishing happened with no notification.
- Configuring a notification recipient would otherwise have meant granting owner privileges.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →