Browse the knowledge centreKnowledge centreMake sense of your workspace.The complete manual 17 chapters · print or save
PRACTICAL GUIDEPro4 min read

Build an alert with a clear outcome

Create a destination, preview a rule against retained evidence, then separately verify the saved configuration and notification delivery.

For Free 1.2.7 and Pro 1.2.7. Check the download page for available versions and requirements. Verify representative workflows on staging before use.

On this page
By the end of this guide

You will know what the rule matches, where it sends minimized facts, whether it is enabled and what the delivery check actually proved.

IN YOUR WORDPRESS WORKSPACE

Logged.ai → Alerts → Advanced alerts

01

Before you start

#

Requires Pro and the relevant alert and investigation access on this site. Start with a single recipient or destination and a clear event condition. Use Free fixed alerts when its predefined email rules already cover the need.

Destination storage requires PHP Sodium and a valid private alert encryption key. Ask the server administrator to follow the one-time setup panel and preserve any existing key. Replacing the key can make encrypted records unreadable.

The read-only public demo shows a disabled fictional rule and destination. It cannot save configuration, enable alerts or send tests. The example below illustrates the current rule editor; it is not evidence of real message delivery.

02

Prepare the destination

#
  1. Complete Set up storage if offered. This creates no enabled rule or destination by itself.
  2. Add a meaningful label and choose WordPress email, signed HTTPS webhook or Slack webhook. For email, choose an eligible WordPress recipient; for a webhook, provide its intended secret URL.
  3. Review the consent to send minimized alert facts, choose whether to enable the destination, then select Save destination. Saving does not send a notification.
  4. If a signing secret is shown, store it privately now. The webhook signing secret is displayed once.
Recipient or webhook requirements

Email recipients need current event and investigation access and a valid email. Use Find an email recipient if the intended eligible account is missing from the bounded list. Webhooks require a public HTTPS destination on port 443; unsupported transport platforms do not send. Treat Slack URLs and signing secrets as credentials.

03

Preview and save the rule

#
  1. For a supported severity rule, use the readable builder to choose its condition, window, minimum count, grouping, cooldown, alert severity and destination. The declarative source remains authoritative for compound rules.
  2. Choose Preview expression. Review both matching-source counts and groups that reach the threshold. A preview examines a bounded retained sample; it neither saves the rule nor sends a notification.
  3. Review the draft’s enabled state. Leave replay unchecked unless you deliberately want retained sources within the rule’s time window to produce new notifications.
  4. Choose Save rule version. Confirm the saved revision, enabled/disabled state and destination. A preview result alone is not a saved rule.

A useful starting example

The supplied default is a high-or-higher severity condition, a 300-second window, a minimum count of 1, site grouping and a 300-second cooldown, initially disabled. Select a real destination, preview the sample and adapt those values to your review process before enabling it.

An exact-event rule in Pro 1.2.7 displays the readable event name, such as Content created, in its saved-rule title. Existing exact-event rules keep their saved conditions, destinations and revision history; the title correction does not enable a rule or change its matching behavior. Compound conditions can still use a generic title: inspect the preserved source and preview before saving.

Pro advanced alert: an exact-event condition. Actual Logged.ai Pro 1.2.7, captured 9 November 2026 in the read-only demo. Fictional sample data dated 19 October 2026.
Pro advanced alert: an exact-event condition

The supported event condition appears as Post changed. This fictional rule and its destination are disabled; the example does not send a test or enable delivery.

Actual Logged.ai Pro 1.2.7, captured 9 November 2026 in the read-only demo. Fictional sample data dated 19 October 2026.Explore this screen in the demo
04

Verify delivery and avoid surprises

#
  1. For an enabled destination, explicitly authorize one Queue synthetic test. This intentionally sends a labelled test to that destination.
  2. Inspect Recent delivery history: distinguish Synthetic test from Rule match, and read status, attempts, acceptance and reason.
  3. Confirm receipt with the recipient or receiving system. Accepted means the transport or WordPress mail subsystem accepted the attempt, not that the message reached its destination.

The synthetic test checks the destination path; it does not establish that a future event will satisfy the rule. The rule still needs suitable evidence, processing and an enabled, available destination.

Editing a webhook requires its URL again, rotates its signing secret and invalidates queued messages for the prior revision. Unknown advanced-delivery attempts may retry with the same delivery ID, so duplicates are possible.

Follow the alert back to its evidence

A real advanced-alert email can link to its triggering event or case. Recent delivery history → Open supporting evidence opens retained references for that rule match. Sign in with an account allowed to review the relevant site and evidence. Removed or expired references remain unavailable; a Synthetic test has no real triggering event. Transport acceptance and an accessible evidence link do not prove inbox delivery.

Read the delivery result conservatively

Mail checks apply to the alert’s own WordPress mail call, including its current message and recipient after final authorization. Other extensions’ nested mail calls are separate. A suppressed or uncertain result is not evidence that the intended inbox received the message. Previously sent messages cannot be recalled.

05

If the outcome is not what you expected

#
The preview is empty

Check the condition, threshold and time window against evidence still retained. The preview is bounded, so zero matches in its sample is not proof that the event never occurred.

The draft cannot be saved

If settings changed since you opened it, keep any necessary nonsecret edits, reload the current saved rule and review the changes. Do not try to bypass the revision guard.

The rule saved but no notification arrived

Check both rule and destination enabled states, then matching evidence, cooldown and Recent delivery history. Follow the recorded reason. A successful save, a preview and a synthetic destination test each prove a different part of the workflow.

ABOUT THIS REFERENCE

This guide covers Logged.ai Free 1.2.7 and Pro 1.2.7. Check available versions and package requirements, and verify representative workflows on staging before updating your main site.

A question we haven’t answered?

Get help with your next step.

Contact support