Slack & Email Notifications for Review Workflow
Once notifications are configured (see Doc Review Workflow States), here’s exactly what gets sent, when, and how.
When a notification fires#
A notification is sent every time a doc’s review status actually changes to something different from what it was, including moving back to No status. Saving a doc without changing its status doesn’t trigger anything. If both email and Slack are configured, both receive the same notification independently, one isn’t a fallback for the other.
Email format#
Sent as a plain text email via WordPress’s normal mail system, one copy per recipient in your comma-separated list. The subject line follows this pattern:
[Docs] "Doc Title" → New Status
The body states who made the change, the doc title, the old and new status, the optional note if one was left, and a direct link to edit the doc.
Slack format#
Sent as a richly formatted message via your incoming webhook, using Slack’s Block Kit rather than plain text. The doc title in the message is a clickable link straight to the doc’s edit screen, so a teammate can jump directly into fixing something flagged as “Changes needed” without hunting for it.
Delivery is fire-and-forget#
The Slack request doesn’t wait for a response and doesn’t hold up saving the doc. This also means a failed delivery, a wrong webhook URL, a deleted Slack app, a network hiccup, fails silently. There’s no retry and no error shown anywhere in WordPress if a Slack notification doesn’t arrive. If notifications seem to have stopped, the most common cause is a webhook URL that’s no longer valid; regenerate it in Slack and update the field under Settings → Workflow.
For developers: hooking in your own integration#
Every status change fires a wpsd_review_status_changed action with the doc ID, new status, old status, the post object, and the note, before email or Slack are handled. If you need a notification channel beyond these two (Microsoft Teams, a custom webhook, a ticketing system), a developer can hook into this same action rather than waiting on a built-in integration.
Was this helpful?
Thanks for your feedback!
✓ Feedback received. Thank you!