If you run a membership site, an LMS, or a blog that takes comments, the WordPress dashboard is a terrible notification center. New users and comments sit under Users and Comments until someone remembers to look.
People search for WordPress new user notification Slack and send WordPress comments to Telegram because they want the event in the tool they already have open. With the AlertHub plugin you map native hooks — user_register and comment_post — and let AlertHub fan them out to every destination you configure.
New user registrations
WordPress fires user_register after a user is created. The first argument is the new user ID ({{0}}).
This is useful when:
- You sell courses or memberships and want to greet (or vet) signups fast.
- Registration should be invite-only and a surprise signup is a red flag.
- A spam wave is creating accounts — you want to see the spike, not a weekly user-count chart.
| Field | Value |
|---|---|
| Hook | user_register (preset: User Registration) |
| Title | New WordPress user #{{0}} |
| Description | A new account was created (user ID **{{0}}**). Review Users in wp-admin if this site is not open to the public. |
| Level | Warning on closed/membership sites; Info on busy open communities |
Closed site vs open community
On a corporate or client site, treat every registration as Warning. On a busy forum, use Info so the dashboard still records volume without waking you at 3 a.m. AlertHub only forwards warning and critical/error to Slack, Telegram, and WhatsApp.
New comments (and spam as a traffic spike)
comment_post runs when a comment is saved. Arguments: comment ID ({{0}}) and approval status ({{1}} — 1, 0, or 'spam').
| Field | Value |
|---|---|
| Hook | comment_post (preset: Comment posted) |
| Title | New WordPress comment #{{0}} |
| Description | Comment ID **{{0}}** saved. Approval flag: **{{1}}**. Moderate it under Comments. |
| Level | Info for approved blogs; Warning if you rarely get comments and each one needs a reply |
If {{1}} is spam, you are looking at a bot wave. That is more useful as a Warning during a campaign or after you disable a captcha.
Published posts (content team)
Editors often want “the post is live” in Slack, not another email.
| Field | Value |
|---|---|
| Hook | publish_post |
| Title | Post published: {{1.post_title}} |
| Description | Post ID **{{0}}** is now public. |
| Level | Info |
publish_post passes $post_ID then $post. {{1.post_title}} uses the plugin’s object-property placeholders. See placeholder docs.
Also consider trashed_post as Warning on production blogs where accidental trash happens.
How teams actually use this
- Support + growth: new users to Slack
#signups, comments to Telegram for the person who replies. - Agencies: source name = client domain; the account manager sees registrations without a WordPress seat.
- Same plugin as security: you already installed AlertHub for failed logins. Adding these hooks is two extra rules, not two extra plugins.
Connect destinations once in the project: getting started. Swap Telegram for Discord later without touching WordPress.
Contact Form 7, WPForms, Gravity Forms
Those plugins expose their own actions (for example wpcf7_mail_sent). The AlertHub UI accepts any hook name, not only the presets.
Example for Contact Form 7:
| Field | Value |
|---|---|
| Hook | wpcf7_mail_sent |
| Title | Contact form submitted |
| Description | A Contact Form 7 message was sent successfully. |
| Level | Warning if leads are rare and valuable; Info if you get dozens a day |
For richer field mapping (name, email, budget), Zapier or Make is often cleaner — see form alerts with Zapier. Use the WordPress hook when you want zero extra SaaS in the critical path.
FAQ
Will comment spam wake me up all night?
Use Info for comment_post and keep Akismet (or your anti-spam plugin) on. Switch to Warning only if comments are rare.
Can I put the user email in the title?
user_register only passes the user ID. Open the user in wp-admin from that ID, or use a small functions.php snippet that loads get_userdata() and calls AlertHub_API::send_alert(). Do not put emails in public Slack channels if contractors can see them.
Does this replace WordPress notification emails?
No. Keep admin emails if you want. AlertHub is the real-time layer with history and multi-channel routing.
Next steps
- Install AlertHub.
- Add
user_registerandcomment_post. - Route Warning events to Telegram or Slack.
Related: plugin and theme security alerts · Zapier form alerts