How Logify PRO Sends Real-Time WordPress Alerts

Waiting to discover an administrator login or a deleted plugin the next time you open the log is too slow for a busy site. Logify PRO's real-time notifications push matching activity to Email, Slack, a generic JSON webhook, or Syslog the moment it happens, so your team responds while the event still matters. You configure everything on one Notifications settings tab and can run several destinations at once.

What are Logify PRO real-time alerts?

Real-time alerts are instant notifications Logify PRO dispatches to an external service whenever a logged activity matches the rules you set for that service. Each notification carries the event details — event type, the user who acted, time, severity, and IP — so the receiver can act without opening WordPress.

Logify PRO ships four notification destinations:

You can enable one destination or all four at the same time, and each one keeps its own event, severity, and rate-limit rules.

Open the Notifications settings tab

Go to Logify → Settings → Notifications. The tab appears only when Logify PRO is active. Every destination is a separate section on this one tab, and every destination is off until you switch its Enable toggle on.

Configure a notification destination

Switch on the Enable toggle for a destination, fill in its connection fields, then set the shared filters described in Filter and rate-limit every destination below.

Email notifications

The Email Notifications section sends matching events as plain-text email alerts.

1. Turn on Enable.
2. In Recipients, enter one email address per line (for example alerts@example.com on one line, security@example.com on the next).
3. Set the shared Send For Event Types, Minimum Severity, and Rate Limit (seconds) filters.
4. Save.

Email suits site owners, freelancers, and compliance reporting where alerts should land directly in an inbox.

Slack notifications

The Slack section posts matching events as Slack attachments through an incoming webhook, so a whole channel sees the activity at once.

1. In Slack, create an Incoming Webhook for the target channel and copy its URL.
2. In Logify, turn on Enable in the Slack section.
3. Paste the URL into Webhook URL (it looks like https://hooks.slack.com/services/...).
4. Set the shared filters and save.
5. Trigger a test event to confirm the message arrives in the channel.

Generic webhook notifications

The Generic Webhook section POSTs the full event payload as JSON to any endpoint, which is how you feed automation platforms, SIEM tools, or custom dashboards.

1. Turn on Enable.
2. Enter your endpoint in Webhook URL (for example https://example.com/hooks/logify).
3. Optionally set an HMAC Secret (optional). When set, Logify signs the request body with HMAC-SHA256 and sends the digest in the X-Logify-Signature header, so your endpoint can verify the request genuinely came from Logify and reject spoofed calls.
4. Set the shared filters and save.
5. Confirm your endpoint receives the test payload.

Syslog (UDP) notifications

The Syslog (UDP) section forwards matching events to a centralized syslog server, so WordPress activity becomes part of your existing logging infrastructure (rsyslog, syslog-ng, Graylog, or a SIEM that accepts syslog).

1. Turn on Enable.
2. In Host, enter your syslog server address (for example syslog.example.com). Enter local to write through PHP's openlog/syslog on the same server instead of sending over a network socket.
3. Set Port (default 514).
4. Set the shared filters and save.


Filter and rate-limit every destination

Every destination shares the same three filters so you send only what matters and avoid alert fatigue:

Because these are per-destination, you can send high-severity security events to Slack while a webhook receives everything. For a full walkthrough of tuning these, see How to narrow Logify PRO alerts by event and severity.

Save and test

Save your settings, then generate a test event — or wait for the next real activity — to confirm delivery. If nothing arrives:

• Re-check the destination's connection field (Recipients, Webhook URL, or Host/Port).
• Confirm the event you triggered passes the Minimum Severity and Send For Event Types filters.
• Check that the Rate Limit (seconds) window has not suppressed the send.
• Verify firewall or network rules allow outbound requests to the endpoint.

Conclusion

Logify PRO real-time alerts move you from checking logs after the fact to hearing about important events as they happen, across Email, Slack, webhooks, and Syslog. Start with one destination and your highest-priority events, then expand as your monitoring grows. Next, tune the per-destination rules in How to narrow Logify PRO alerts by event and severity, or review what each event means in the event reference.

FAQs

Does the free version of Logify send real-time alerts?

No. The free plugin includes only the scheduled Email Digest, which is a periodic summary email sent daily, weekly, or monthly. Live, per-event alerting to Email, Slack, a webhook, or Syslog is a Logify PRO feature configured on the Notifications settings tab. If you need to be notified the moment an event occurs, you need Logify PRO.

Can I send alerts to more than one destination at once?

Yes. Email, Slack, Generic Webhook, and Syslog are independent sections on the Notifications tab, each with its own Enable toggle. You can turn on any combination and give each destination its own event-type filter, minimum severity, and rate limit. For example, Slack can receive only critical security events while a webhook receives everything for archival.

How do I verify a Logify webhook request is genuine?

Set an HMAC Secret in the Generic Webhook section. Logify then signs each request body with HMAC-SHA256 using that secret and sends the resulting digest in the X-Logify-Signature header. Your endpoint recomputes the HMAC over the received body with the same secret and compares it to the header, rejecting any request where the signatures do not match.

Why am I not receiving notifications after enabling a destination?

Check the filters first. A destination only fires for events that pass its Minimum Severity (default Warning/300) and Send For Event Types rules, so a low-severity or unchecked event type is skipped. Also confirm the Rate Limit (seconds) window has not suppressed a repeat send, that the connection field is correct, and that your firewall allows outbound requests.

What is the difference between the Email destination and the Email Digest?

The Email destination is a real-time PRO alert sent the instant a matching event occurs. The Email Digest is a scheduled summary of activity over a period, available in the free plugin. Use the Email destination for immediate awareness of individual events, and the digest for a regular recap of overall site activity.