PushPing lets your Bubble app send native browser push notifications triggered from any workflow — "order shipped," "new message," "task due," anything. Notifications arrive through the browser's own notification system, so they work even when the tab is closed, and each user can be subscribed on multiple devices/browsers at once (their phone and laptop both get notified).
Built on the standard Web Push protocol (VAPID), so it works across Chrome, Edge, and Firefox on Windows/macOS/Android without any native app or app store submission. iOS/iPadOS is supported when the app is added to the Home Screen (Apple's requirement, not a plugin limitation).
Setup requires:
sw.js) to your app's root file hostingNo paid third-party service required — notifications are sent directly from your Bubble app's own backend.
An invisible element you place on any page where you want to offer notification opt-in (e.g. a settings page, or right after signup).
States:
| State | Type | Description |
|---|---|---|
subscription_json |
text | The subscription payload for this browser/device. Save this to the user's record. |
Events:
| Event | Fires when |
|---|---|
subscription_ready |
A subscription was successfully created |
permission_denied |
The user declined the browser's notification permission prompt |
subscription_unsupported |
The current browser doesn't support push (rare, very old browsers) |
subscription_error |
Something went wrong creating the subscription |
ios_needs_home_screen_install |
User is on iOS(16.4+) Safari, Chrome, etc but hasn't installed the app to their Home Screen yet — push isn't possible until they do |
Actions (element actions, used in workflows):
| Action | What it does |
|---|---|
Subscribe to notifications |
Requests permission and creates a push subscription for the current browser |
Used in any backend or frontend workflow to actually send a push.