Notificator inbox
Keep connected alerts together inside the mobile app.
Get started
Use WordPress, Strapi, or the Node.js SDK to turn meaningful events into alerts for the Notificator inbox, phones, email, and compatible devices.
Both integrations provide a useful local destination before anything leaves your website.
Start from discovered hooks or ready-made templates. Configure everything locally before deciding whether any alert should leave your WordPress site.
Install Notificator from the official WordPress.org directory, activate it, and open Notificator from your dashboard.
Scan active plugins, review plain-language event descriptions, or begin with a curated notification template.
Choose an event, write a useful title and message, and keep Dashboard enabled. This local path needs no account or API key.
Add a WordPress API key from the mobile app when you want the Notificator inbox, mobile push, email, or MQTT devices.
Create named rules from Strapi 5 content operations, keep secrets on the server, and begin with local panel activity while the extension is in preview.
npm install @notificator-project/strapi-extension Add the preview package to a Strapi 5 project, enable it in config/plugins.ts, and restart the application.
Create a named rule for an application content type and choose created, updated, published, unpublished, or deleted.
Build a readable message and enable the Strapi activity log. Local history and admin toasts need no account or API key.
Store a Strapi API key in the server environment to enable the Notificator inbox, mobile push, email, or MQTT delivery.
Connect backends, workers, serverless functions, and internal services to the hosted Notificator API without managing delivery infrastructure yourself.
npm install @notificator-project/api Add the official package to a Node.js 20 or newer backend, serverless function, queue worker, or trusted server environment.
Create a Public API key in the mobile app and store it in a server environment variable. Never expose it in browser code.
Initialize NotificatorClient with your server-side key. The SDK uses the hosted Notificator API and provides structured errors.
Provide a title and optional body, source, severity, and data, then choose push, email, and MQTT delivery controls.
Optional shared path
Install the mobile app, create the API-key type that matches your integration, and enable only the destinations that are useful for each rule.
Keep connected alerts together inside the mobile app.
Receive push alerts and use the account-level email preference.
Use your own HiveMQ Cloud connection with compatible Notificator firmware.
Optional physical alerts
Notificator devices receive selected alerts through your own MQTT connection. Build the compact Base model, use the touchscreen model, or follow the next hardware target as it develops.
A compact ESP32-C3 device with an OLED display and capacitive control. Build it from accessible components and open-source firmware.
A supported Waveshare ESP32-S3 touchscreen with alert history, audio, controls, and an idle clock and weather view.
An upcoming device path designed to let selected Notificator alerts trigger compatible smart-home and office devices.