Push Notifications for Trigv

Trigv watches the WordPress events (Triggers) you choose and dispatches them as push notifications through the Trigv API. Dispatch happens asynchronously in the background, with retries, so your site stays fast.

• Pick from a curated catalog of WordPress Triggers.
• Map each Trigger to a Trigv channel and level, with an optional custom title/description template.
• Fire your own notifications from code with do_action( 'trigv_send', $args ).
• Shape or veto any notification with the trigv_dispatch_args and trigv_pre_dispatch filters.
• Add-ons can register more Triggers via the trigv_triggers filter.

Developer API

Full developer guide (custom Triggers, filters, REST API, examples): DEVELOPER.md

Configuration

Set the API key on the Trigv admin screen, or define it in wp-config.php:

External services

This plugin connects to Trigv, a third-party push-notification service, to deliver the WordPress events you choose as notifications on your devices.

When a Trigger you have enabled fires — or you send a test notification, or you call do_action( 'trigv_send', ... ) — the plugin sends an HTTPS request to the Trigv API at https://api.trigv.com. Each request includes:

• the notification channel, title, and (optionally) description, level, event type, delivery urgency, image URL, and an idempotency key;
• your Trigv API key, sent as an Authorization request header;
• a User-Agent request header identifying the plugin and its version.

No data is sent until you enter a Trigv API key and enable at least one Trigger (or trigger a manual/test send). Trigv stores only event metadata such as timestamps, delivery status, and usage counts; notification content is delivered to your devices and is not retained on Trigv servers.

Service provider: Webtions OÜ (dba Trigv). Terms of Service: https://trigv.com/terms Privacy Policy: https://trigv.com/legal/privacy-policy