WordPress Plugin

The FlowAlert plugin connects your WordPress site to FlowAlert — no custom code required. It covers six families of integration:

• WordPress itself — fatal errors (recovery mode), failed auto-updates, administrator logins, plugin & theme changes, new user registrations. No third-party plugin needed.
• Site heartbeat — the plugin checks in with FlowAlert every 10 minutes; if your site goes silent, FlowAlert pages whoever is on call.
• Forms — Contact Form 7, WPForms, Forminator, SureForms, Ninja Forms, Fluent Forms, Gravity Forms, Elementor Pro Forms, Formidable Forms, Divi, and Jetpack Forms.
• eCommerce — WooCommerce (orders, status changes, refunds, subscriptions, low/out-of-stock, failed payments) and Easy Digital Downloads.
• Bookings — Amelia, FluentBooking, LatePoint, MotoPress Hotel Booking, and Five Star Restaurant Reservations.
• Support & donations — Fluent Support and GiveWP.

Each integration is detected automatically — a detected / not detected badge appears next to its name — and each is off until you enable it.

Installation

1. In your WordPress admin go to Plugins → Add New and search for FlowAlert
2. Click Install Now then Activate

Alternatively, download the zip from wordpress.org/plugins/flowalert (opens in a new tab) and install via Plugins → Add New → Upload Plugin.

Connect your API key

Go to Settings → FlowAlert:

Click Save Settings.

Verify the connection

Click Send test alert. You can test before saving — the button uses the key currently in the field, not the last saved value.

If you see "✓ Test event sent!", the connection is working. Check Dashboard → Alerts to confirm the event arrived.

WordPress site events

The 🖥️ Site health → WordPress card needs no third-party plugin — it alerts on the operational events WordPress itself emits. Each toggle is off by default:

All five share one Priority setting (fatal errors override it to URGENT).

Site heartbeat

Under ⚙️ General → Site Heartbeat, the plugin pings a FlowAlert heartbeat monitor every 10 minutes via WP-Cron. If the site stops checking in — host outage, fatal crash, suspended account, broken cron — the silence pages whoever is on call.

Setup is one checkbox (plugin 1.2.0+): tick Enable heartbeat and save. Using your API key, the plugin asks FlowAlert to create this site's monitor (30-minute interval, 15-minute grace) and fills the check-in URL in automatically. Enabling it on the same site again reuses the same monitor — nothing is duplicated.

Prefer manual control? Create a monitor yourself under Heartbeats → New (interval 30–60 minutes) and paste its check-in URL into the field — a pasted URL always wins over auto-setup.

For traffic-independent monitoring, also flip on the Uptime check on the site's card (Dashboard → Sites): FlowAlert visits your site from the outside every few minutes and fires site.down after three consecutive failures — no plugin, cron or traffic involved. The two signals complement each other.

The heartbeat authenticates by its unguessable URL token, so it works even before an API key is entered.

Forms

The plugin integrates with eleven form plugins, each detected automatically:

Configuring a form integration

Every form integration has the same options:

Contact Form 7 has two additional fields:

When you enable an integration, the plugin automatically seeds the event type into your FlowAlert dashboard so it appears in the routing rule builder straight away.

Setting up routing rules for forms

In your FlowAlert dashboard, create a routing rule with the event key you configured above (default form.submitted):

• Event key: form.submitted (or your custom key)
• Target group: the group you want to notify
• Requires ACK: match the setting you chose in the plugin

If you have multiple form types and want them to notify different people, give each integration a different event key (e.g. booking.submitted, contact.submitted) and create a rule for each.

WooCommerce

When WooCommerce is active, the plugin sends an alert every time a new order is placed.

The plugin hooks into both woocommerce_checkout_order_created (classic checkout) and woocommerce_store_api_checkout_order_processed (block checkout). Built-in deduplication ensures only one notification fires per order even if both hooks run.

Data included in every order.created event:

You can use these fields in routing rule filter conditions — for example, to route orders over a certain total to a different group.

Additional WooCommerce alerts

Each of these is off by default — enable them individually in the plugin settings:

Each event carries the relevant data.* fields and sets a dedupeKey, so a given transition fires once even if the underlying hook runs twice.

Easy Digital Downloads

When Easy Digital Downloads is active, the plugin sends an alert on every completed purchase.

Data included in every purchase.completed event: payment_id, total, currency, customer_name, customer_email, items, item_names, site.

Create a routing rule with event key purchase.completed.

Bookings

For booking plugins that expose WordPress hooks, FlowAlert is a one-click toggle — no webhook to wire up. Enable the integration under 📅 Bookings and a booking pushes the moment it's made.

Each event carries the customer name, email, start time, and (where available) the service. Create a routing rule with event key booking.created — and booking.cancelled if you've enabled cancellations — and point them at your front-desk group.

Support & Donations

Both follow the same pattern as the other one-click integrations:

• Fluent Support carries the customer, subject, and priority — route ticket.created to your support group and pair it with an escalation policy to enforce an SLA.
• GiveWP carries the amount, currency, and donor — route donation.received to your fundraising team.

Plugins that connect a different way

The one-click integrations above work because each plugin exposes a WordPress action hook the FlowAlert plugin can listen on. Some popular plugins don't — either they're closed-source (no hooks) or they keep their data in their own tables. The FlowAlert plugin can't drive these directly, but they can still reach FlowAlert through their own webhook, the REST API, or Zapier.

This isn't a one-click toggle — it's a few minutes of setup in that plugin's own settings — but no code is involved. The full step-by-step for each lives in Webhooks & Automation.

Email fallback

Under General in the settings page, you can enable an email fallback. If the FlowAlert API is unreachable when an event fires, the plugin will send a plain email via wp_mail so the alert is not silently lost.

Agencies & fleets

Everything above assumes one site. If you look after many — an agency with 22 client installs, a franchise, a network — the plugin and API are built to onboard the whole fleet in minutes, into one FlowAlert workspace.

Each install identifies itself on every event, so the dashboard's Sites page fills in automatically: one row per site with its health, open alerts, check-in state and uptime-check status, and every push is prefixed with the site's name ([Acme Bakery] Fatal error) once a second site appears. Uptime checks are enabled per site from the same card — worth flipping on for every client site that matters (plans cap how many sites can have it on at once: 1 on Free, 5 on Pro, 50 on Agency).

Configure via wp-config.php

Instead of pasting the API key into each site's settings screen, define it in code (plugin 1.2.0+):

define( 'FLOWALERT_API_KEY', 'fa_live_your_workspace_key' );
// Optional — only when self-hosting or pointing at staging:
define( 'FLOWALERT_API_URL', 'https://api.flowalert.io/v1' );

A defined constant always wins over the saved option, and the settings screen shows the field as managed by code. This is the natural fit for provisioning tools, site templates, and hosts that template wp-config.php.

Configure via WP-CLI

The plugin stores plain WordPress options, so the whole setup scripts cleanly:

# Install, activate, connect
wp plugin install flowalert --activate
wp option update flowalert_api_key "fa_live_your_workspace_key"
 
# Turn on the site's own alarms + dead-man's switch
wp option update flowalert_site_fatal_enabled 1
wp option update flowalert_site_update_enabled 1
wp option update flowalert_heartbeat_enabled 1
 
# Enable the integrations this site uses (one option per integration)
wp option update flowalert_woo_enabled 1     # WooCommerce
wp option update flowalert_cf7_enabled 1     # Contact Form 7
wp option update flowalert_gf_enabled 1      # Gravity Forms

Every toggle on the settings screen follows the same flowalert_*_enabled pattern — enable exactly what each site runs. The heartbeat provisions itself on the next wp-admin page load (or immediately if you enable it from the settings screen).

Run it across the fleet with a loop:

for site in site-a site-b site-c; do
  wp @$site plugin install flowalert --activate
  wp @$site option update flowalert_api_key "fa_live_your_workspace_key"
  wp @$site option update flowalert_site_fatal_enabled 1
  wp @$site option update flowalert_heartbeat_enabled 1
done

(@site-a style aliases come from your WP-CLI config (opens in a new tab).)

MainWP / ManageWP

From a management console, the recipe is the same two steps:

1. Bulk-install the FlowAlert plugin from the WordPress.org repository to the selected sites (MainWP: Plugins → Install; ManageWP: Plugins → Add).
2. Push the key: add the FLOWALERT_API_KEY line to each site's wp-config.php (MainWP's Code Snippets extension can inject it fleet-wide), or run the WP-CLI commands above through your host's terminal.

Once events start arriving, each install registers itself under Sites in your dashboard — rename any of them to the client name you actually use, and route alerts per site with a routing-rule condition on data.site.