Skip to content
Notificator Docs

Complete Workflow

This guide connects all setup pieces in the recommended order.

Step 1: Choose the source integration

Section titled “Step 1: Choose the source integration”

Use the integration that owns the events you want to watch.

WordPress

Section titled “WordPress”

Install Notificator and open Notificator → Overview.

  • Scan active plugins to discover events.
  • Apply a template or create a notification from a discovered event.
  • Leave Dashboard enabled as the delivery channel.

No Notificator account or API key is needed for dashboard notifications. Continue with WordPress Plugin Setup.

Strapi

Section titled “Strapi”

Install @notificator-project/strapi-extension, register it in config/plugins.ts, and open Notificator in Strapi admin.

  • Create rules for application content types.
  • Choose created, updated, published, unpublished, or deleted.
  • Enable Strapi activity log for local delivery.

No Notificator account or API key is needed for the local Strapi activity feed. Continue with Strapi Extension Setup.

Step 2: Verify local delivery

Section titled “Step 2: Verify local delivery”

Trigger the event and check the integration’s activity view. WordPress dashboard events can show a wp-admin toast. Strapi rules with Strapi activity log keep the newest 100 matches locally and can show a Strapi admin toast.

In WordPress, each notification has a Dashboard toggle, while Settings provides global toast controls, conditions, and throttling. In Strapi, enable the local activity choice on each rule; the extension checks for new local toast activity while the admin panel is open.

Step 3: Connect remote delivery (optional)

Section titled “Step 3: Connect remote delivery (optional)”

Create an account and server API key only if you want the Notificator inbox, mobile push, email, or MQTT.

  • Sign in to the mobile app.
  • Create a WordPress (wordpress_server) key for WordPress.
  • Create a Strapi Extension (strapi_server) key for Strapi.
  • In WordPress, add and enable the key under Notificator → Settings → Remote delivery.
  • In Strapi, store it as NOTIFICATOR_API_KEY and restart the server.
  • Enable the remote channels required by each notification or rule.

Continue with Create API Key (Mobile).

MQTT also requires your own HiveMQ Cloud cluster. Notificator does not provide a default broker. Configure the same cluster and topic prefix in WordPress or Strapi and on the device by following MQTT Broker Setup.

Step 4: Add plugin templates and hook integrations

Section titled “Step 4: Add plugin templates and hook integrations”

If you are a plugin/theme developer and want deeper integration:

  • Create reusable scenario templates that appear in Notificator UI.
  • Register custom events with accurate descriptions and payload field names.
  • Emit normal WordPress actions and let administrators choose their delivery channels.

Continue with:

Step 5: Configure app settings

Section titled “Step 5: Configure app settings”

Tune notifications, security, and home widgets from mobile settings.

  • Enable push for current device.
  • Review notification preferences.
  • Configure 2FA and visibility options.

Continue with App Settings Guide.

Step 6: Configure a Notificator device (optional)

Section titled “Step 6: Configure a Notificator device (optional)”

If you use a physical Notificator device:

  • Choose Base or Touch when adding the device in the mobile app.
  • Set idle theme (Clock, Weather, or Weather & Clock).
  • Configure weather location/timezone as needed.
  • Adjust the model’s supported display and sound controls.

Continue with Notificator Base Setup or Notificator Touch Setup.

Step 7: Validate external API flow

Section titled “Step 7: Validate external API flow”

Use OpenAPI and samples to test your public-notify payloads.