Appushy

Appilix turns your WordPress site into a native Android/iOS app. It gives you a Push Notification API and a user-identity mechanism, but using either from WooCommerce order events requires writing and hosting your own integration code — not realistic for Appilix’s largely no-code audience.

Appushy closes that gap. Connect your Appilix App Key and API Key, turn on the order statuses you want to notify customers about, and Appushy handles the rest: identifying which customer to notify, sending the push, and logging what happened — automatically, every time an order changes status.

What Appushy does

• Connects to your Appilix app with your App Key and API Key, and validates them before you rely on them.

• Sends a native push notification when a WooCommerce order reaches a status you’ve turned on — Processing, Completed, On Hold, Refunded, and more.

• Sends a native push notification automatically when a student enrols in a Tutor LMS course — free, no Pro license needed.

• Sends a native push notification automatically when someone gets a new direct message via Better Messages — free, no Pro license needed.

• Identifies customers automatically, including guest checkouts, so pushes reach the right device without the customer doing anything extra beyond opening the app once.

• Every trigger’s notification lives on one screen — Appushy → Push Automation — where you can see, and toggle, exactly what gets sent and when.

• Logs every send attempt (last 100, with automatic pruning after however many days you choose) so you can see what was actually sent, and why a customer who hasn’t opened the app yet didn’t receive anything.

• Retries automatically for a few minutes when a customer’s device isn’t registered with Appilix yet — a common, expected timing gap right after checkout, not a failure.

What Appushy needs from you first

Appilix’s Push Notification module requires Firebase to be connected on the Appilix side before any of this works — 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 (Firebase project, Cloud Messaging enabled, app rebuilt and reinstalled with the new configuration baked in).

Honest limitations

• Push notifications reach app installs only — not browser visitors. That’s a different technology (browser push), not something this plugin does.

• A customer must have opened your app and been identified at least once before a targeted push can reach their device. Appushy handles the identification automatically once that’s happened.

• Delivery depends on Appilix and Firebase Cloud Messaging. Appushy logs that it successfully handed a notification to Appilix’s API — not that a specific device actually displayed it.

• The Push Notification API is a paid Appilix module, not available on Appilix’s free trial.

txt.

External Services

com) to send native app push notifications. This is required for the plugin’s core functionality — without it, no notification can be sent.

What is sent, 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 an order reaches a status you’ve enabled a notification for, and when you use “Send test push.”

com/api/push-notification-token ) — never through any third-party server other than Appilix’s own.

com/privacy-policy.