Appushy

By Shafayat Hossain

0+ active installationsVersion 2.0.0

Free browser push notifications from your own server, plus Appilix app pushes, for new posts, WooCommerce orders and more.

Description

Appushy sends real push notifications straight from WordPress. Turn on web push and it works immediately — no account, no API key, no third-party service — or connect an Appilix app to also reach your native Android/iOS app. Run both at once if you want: one event, pushed to everyone who can receive it.

What Appushy does, free

  • Web push, built in — visitors opt in from a prompt on your site and start receiving notifications straight away. No account to create, nothing to configure beyond turning it on.
  • Automatic push when you publish a post, page, product, course, or any custom post type you choose — the single most common reason anyone installs a push plugin.
  • Connects to an Appilix app with your App Key and API Key, and validates them before you rely on them, if you also want to reach a native app.
  • Sends a push when a WooCommerce order reaches a status you’ve turned on — Processing, Completed, On Hold, Refunded, and more, all seven order statuses, free.
  • Sends a push automatically when a student enrols in a Tutor LMS course, and when someone gets a new direct message via Better Messages — both free, no Pro license needed.
  • Manual send to everyone, from one screen, with a live preview and a test send to yourself first.
  • Choose exactly which channels (web push, Appilix, or both) a given send or automation reaches — free on every plan, never gated.
  • Unlimited subscribers, unlimited channels, no send caps — ever.
  • Every send and automation lands on one screen — Appushy → Logs — with delivery status, so you can see what actually went out and why.
  • Subscriber list with search, filtering, and CSV export; GDPR tools for consent, export, and erasure.
  • System Health diagnostics tell you before launch whether your server is ready for web push.

What Pro adds

  • Audience segmentation — target a send by role, device, browser, or the page someone visited, instead of sending to everyone.
  • Recurring sends — schedule a notification to repeat on its own.
  • Per-channel content variants — different title, message, and link per channel from one send, instead of the same text going everywhere.
  • Priority support.

What Appushy needs from you first

Web push works the moment you turn it on — nothing else required. If you also want to reach a native app, Appilix’s Push Notification module requires Firebase to be connected on the Appilix side first — that’s an Appilix-side setup step, not something Appushy can do for you. See “Before you start” in the plugin’s own documentation, linked from the Settings screen, for the full checklist.

Honest limitations

  • Web push reaches browsers that support it and have granted permission — not every browser. Safari on iOS only supports it once a visitor adds your site to their home screen.
  • Appilix push reaches app installs only — not browser visitors. A customer must have opened your app and been identified at least once before a targeted push can reach their device.
  • Delivery for Appilix sends depends on Appilix and Firebase Cloud Messaging; Appushy logs that it successfully handed a notification to Appilix’s API, not that a specific device displayed it. Web push delivery depends on each browser’s own push service (Google, Mozilla, Apple) in the same way.
  • The Appilix Push Notification API is a paid Appilix module, not available on Appilix’s free trial.

This plugin bundles the Plus Jakarta Sans, Instrument Serif, and JetBrains Mono typefaces (SIL Open Font License 1.1) for its setup wizard — see assets/fonts/OFL.txt.

Requirements

  • WordPress 6.2 or higher.
  • PHP 7.4 or higher.
  • To use the Web Push channel (browser notifications sent from your own server) specifically: PHP 8.1 or higher, HTTPS, and the PHP openssl extension with elliptic curve (EC) support — nearly every host has this by default. None of this is needed if you only use Appilix app push notifications; Appushy’s System Health screen tells you exactly what, if anything, your host is missing, and gives you copy-ready text to send your host’s support team.
  • Recommended, not required, for Web Push: the PHP gmp or bcmath extension. Either one speeds up sending to large subscriber lists; without both, Web Push still works, just somewhat slower.

External Services

This plugin can send push notifications through two different services, depending on which channels you enable.

Web Push (built in, no account needed): when you enable the Web Push channel, this plugin uses the bundled minishlink/web-push PHP library to deliver notifications directly to each subscriber’s browser, through that browser’s own push service — Google (Chrome, Edge, and other Chromium browsers), Mozilla (Firefox), or Apple (Safari). This happens directly from your WordPress server to the browser vendor’s own push endpoint — never through any Appushy-operated server — and only when a visitor has opted in and you send or an automation fires. See each vendor’s privacy policy: Google (https://policies.google.com/privacy), Mozilla (https://www.mozilla.org/privacy/), Apple (https://www.apple.com/legal/privacy/).

Appilix (optional, only if you connect an app): if you enter an Appilix App Key and API Key, this plugin connects to the Appilix push notification service (https://appilix.com) to send native app push notifications.

What is sent to Appilix, and when:

  • Your Appilix App Key and API Key (entered by you in Settings) are sent with every request, to authenticate it as coming from your app.
  • A customer identity — either the customer’s email address or their WordPress user ID, depending on which you choose under Settings → Identify customers by — is sent so Appilix can target the notification to the right device. This is sent both when a customer logs in or completes checkout (to register their identity with Appilix) and with every notification (to target it).
  • The notification title and message text, which may include the customer’s first name, the order number, and the order total, substituted into the message. This is sent every time a notification you’ve enabled fires, and when you use “Send test push.”

This data is sent directly from your WordPress server to Appilix’s API (https://appilix.com/api/push-notification and https://appilix.com/api/push-notification-token) — never through any third-party server other than Appilix’s own. Appilix’s Terms of Service and Privacy Policy govern how this data is handled once received: https://appilix.com/terms-conditions and https://appilix.com/privacy-policy.

Announcement list (Google Apps Script): If you tick “Tell me when new integrations ship” during setup, Appushy sends your email address, your site’s address, and the time to a Google Apps Script endpoint (script.google.com), so we can email you about new integrations. This only happens if you tick that box — it is off by default.

Google’s Terms of Service
Google’s Privacy Policy
Appushy’s Privacy Policy

Installation

  1. Upload and activate Appushy like any WordPress plugin, or install it directly from the WordPress Plugin Directory.
  2. A short guided setup wizard appears automatically after activation. Choose Web Push to start receiving notifications immediately with no external account, or App Platform to connect an Appilix app instead (or set both up — you can always add the other channel later from Platforms).
  3. Prefer to skip the wizard? Use “Skip setup” on any step to go straight to Appushy → Platforms, where you can connect and test each channel manually at any time.
  4. Works with WooCommerce, Tutor LMS, and/or Better Messages — activate whichever you use; Appushy detects each one automatically and never requires any of them just to install. New-post pushes work with no third-party integration — Appushy uses WordPress’s own scheduling when a faster background library isn’t available.
  5. Go to Appushy → Push Automation and turn on the events you want to notify about.

FAQ

Do I need Appilix, or a paid plan, to use this plugin?

No. Web Push is free, built in, and needs no third-party account at all — it’s the fastest way to start sending notifications. Appilix is entirely optional, for reaching a native Android/iOS app; if you do connect one, its Push Notification API is a paid Appilix module (not available on Appilix’s free trial), and needs Firebase connected on the Appilix side — see “Before you start” in the plugin’s documentation.

Why isn’t a subscriber or customer receiving notifications?

For Appilix, almost always because they haven’t opened your app and been identified yet — Appushy’s log will show “Not delivered — Hasn’t opened your app yet” for these, which is the expected, normal outcome, not an error. For Web Push, the most common cause is the subscriber’s browser permission being revoked or their device going offline for a long period — Appushy marks that subscriber “Inactive” automatically rather than keep retrying indefinitely.

Why do automatic notifications sometimes arrive a minute or so late?

That’s a background task scheduler (Action Scheduler, bundled with WooCommerce/Appushy Pro — Appushy falls back to WordPress’s own wp-cron on a free-only install), not Appushy or Appilix — by default it only runs when someone visits your site, so on a quiet site a notification can wait briefly for the next page load before it’s sent. For instant delivery regardless of traffic, set up a real server cron job instead of WordPress’s default (define( 'DISABLE_WP_CRON', true ); in wp-config.php, plus a real cron entry hitting wp-cron.php — most hosts support this, and it’s the same fix WooCommerce recommends for order-processing timing). Manual sends aren’t affected — those go out immediately.

Does this work for guest checkouts?

Yes, when identifying Appilix customers by email (the default). Appushy registers the order’s billing email with Appilix automatically on the order-confirmation page, whether or not the customer has an account. Web Push subscribers don’t need an account or checkout at all — anyone who opts in on your site can receive notifications.

Can I customize the notification text?

Not in the free version — every trigger has fixed, pre-written text with variables like the customer’s name and order number filled in automatically. Editing that text per event, and saving it so it’s reused across sends, is a Pro feature.

Is my data safe?

Your Appilix App Key and API Key are never displayed after saving (masked in the UI) and never appear in the notification log. See “External Services” above for exactly what’s sent to Appilix, and to each browser vendor for Web Push, and when.

Screenshots

Changelog

2.0.0

  • New: Web Push — a built-in, free notification channel with no third-party service required.
  • New: Automatic push when you publish a post, page, product, course, or any custom post type.
  • New: Entirely new admin interface across every screen.
  • New: Choose exactly which connected channels a send or automation reaches.
  • Pro: Audience segmentation — target by role, device, browser, or page visited.
  • Pro: Recurring sends.
  • Pro: Per-channel content variants — different content per channel from one send.
  • Fix: saving Settings could silently reset Appilix’s “Match subscribers by” option back to email, even when you’d set it to User ID.
  • Fix: sending to a segment now shows the correct recipient count, automatically unchecks Appilix when a segment can’t reach it, and blocks a send against a segment with no matching subscribers instead of sending to nobody silently.
  • Fix: the three opt-in prompt styles (banner, modal, corner) now actually look different from each other, and the “Your own button” trigger option works.
  • Change: “Don’t show it on these pages” now matches a page exactly, or as a prefix when the pattern ends with * (e.g. /my-account/* matches every My Account sub-page), instead of matching anywhere in the URL. A short pattern like shop no longer also catches unrelated pages like /workshop — if you want a page excluded, list its exact address (or an address ending in * for everything under it, e.g. /shop/*).
  • Fix: several accuracy and display fixes across Dashboard, Logs, and Audience — including honest delivery-rate wording, correct order/skipped-status labels, and page-exclusion/overlap display issues.
  • Security: added rate limiting to the public subscribe endpoint, stopped the push encryption key from loading on every page request, and removed Shop Manager access to destructive admin actions (key regeneration, credential changes, uninstall settings).

1.0.1

  • New: Added Dashboard Page.
  • New: Added Free vs Pro comparison page.

0.0.1

  • Initial release.
  • Appilix connection: App Key/API Key with Validate.
  • WooCommerce order-status push notifications — Push Automation screen, on/off per status.
  • Automatic customer identification, including guest checkouts.
  • Notification log with configurable retention.
  • Automatic retry when a customer’s device isn’t registered yet.
  • Tutor LMS: automatic enrollment push notifications.