Get started

Start with the path that fits your stack.

Use WordPress, Strapi, or the Node.js SDK to turn meaningful events into alerts for the Notificator inbox, phones, email, and compatible devices.

WordPress and Strapi can start locally. No account or API key

Both integrations provide a useful local destination before anything leaves your website.

WordPress Dashboard alerts Strapi Panel activity
WordPress path

Turn site events into dashboard alerts in a few focused steps.

Start from discovered hooks or ready-made templates. Configure everything locally before deciding whether any alert should leave your WordPress site.

  1. 01

    Install the WordPress Plugin

    Install Notificator from the official WordPress.org directory, activate it, and open Notificator from your dashboard.

  2. 02

    Discover your site events

    Scan active plugins, review plain-language event descriptions, or begin with a curated notification template.

  3. 03

    Create your first alert

    Choose an event, write a useful title and message, and keep Dashboard enabled. This local path needs no account or API key.

  4. 04

    Connect more destinations when ready

    Add a WordPress API key from the mobile app when you want the Notificator inbox, mobile push, email, or MQTT devices.

Strapi path

Build content lifecycle alerts that remain native to Strapi.

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
  1. 01

    Install the Strapi Extension

    Add the preview package to a Strapi 5 project, enable it in config/plugins.ts, and restart the application.

  2. 02

    Choose a content event

    Create a named rule for an application content type and choose created, updated, published, unpublished, or deleted.

  3. 03

    Start with panel activity

    Build a readable message and enable the Strapi activity log. Local history and admin toasts need no account or API key.

  4. 04

    Add connected delivery when useful

    Store a Strapi API key in the server environment to enable the Notificator inbox, mobile push, email, or MQTT delivery.

Developer path

Send application events through the official Node.js SDK.

Connect backends, workers, serverless functions, and internal services to the hosted Notificator API without managing delivery infrastructure yourself.

npm install @notificator-project/api
  1. 01

    Install the Node.js SDK

    Add the official package to a Node.js 20 or newer backend, serverless function, queue worker, or trusted server environment.

  2. 02

    Create a Public API key

    Create a Public API key in the mobile app and store it in a server environment variable. Never expose it in browser code.

  3. 03

    Create the client

    Initialize NotificatorClient with your server-side key. The SDK uses the hosted Notificator API and provides structured errors.

  4. 04

    Send your first alert

    Provide a title and optional body, source, severity, and data, then choose push, email, and MQTT delivery controls.

Optional shared path

Connect Notificator when alerts need to travel further.

Install the mobile app, create the API-key type that matches your integration, and enable only the destinations that are useful for each rule.

WordPress WordPress key Strapi Strapi Extension key Node.js SDK Public API key
01

Notificator inbox

Keep connected alerts together inside the mobile app.

02

Mobile and email

Receive push alerts and use the account-level email preference.

03

MQTT devices

Use your own HiveMQ Cloud connection with compatible Notificator firmware.

Optional physical alerts

Build a device or start with supported hardware.

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.

BASEStable firmware

Notificator Base

A compact ESP32-C3 device with an OLED display and capacitive control. Build it from accessible components and open-source firmware.

Next steps

Continue with the part you need next.