Plugin Announcement: Engage your customers with OneSignal web notifications

We are excited to launch the official OneSignal plugin for Bubble! OneSignal is the market leader in customer engagement, powering dynamic and easy-to-use push notifications. In an age where everyone is vying for consumers’ attention, it is important to engage with your customers smarter, not harder. Enter OneSignal - you can now easily incorporate personalized or mass notifications in your Bubble app, with a plugin built by Bubble in partnership with OneSignal. After seeing so much interest in OneSignal from our users, we set out to create a plugin that makes sending push notifications from a Bubble application more streamlined than ever before!

To get you as excited as we are, here are 3 example workflows made possible by the OneSignal plugin:

1. Maintaining Interest

Web notifications can be a great way to re-engage with a customer who has already shown interest in a product or feature of your application.

Example: For an out-of-stock product, create a button next to it that says, “Notify me when this item is back in stock.” Prompt the consumer to enable notifications and tag them as interested in that product. That way, you can increase your likelihood of making the sale even without a product on hand.

2. Instant Messaging

For apps that have a messaging or social media feature, use push notifications to keep your users engaged in your application even when they’re offline. This is a great way to increase user engagement and retain users over time.

Example: When a user comments on a post, let the author of that post know that they’ve received a comment by sending them a direct push notification! Not only will this engage users with your application, but it will help build a community within your application as well.

3. Announcements

For big changes in your company or application, keep your entire subscribed user base up-to-date with the latest news. You can easily send notifications to all subscribed users and reach them in a way that has a more personal feel than email alone.

Example: Say you, I don’t know, released a really cool new feature on your application and wanted to let all of your subscribers know (sound familiar?). You can easily do so either within Bubble or the OneSignal dashboard. You could even set up a Scheduled API Workflow in Bubble to automatically send out the notification when the timing is right.

Push notifications are an easy, personal way to engage customers and make your application more dynamic. Bring your app directly to your users today by installing the OneSignal plugin in the Plugins tab.

To get started: OneSignal Web Notifications - Bubble Docs
For tips on how to craft effective notifications: Best Practices - Push Notification & Messaging Blog


This is great! But… I can’t find the plugin :male_detective: :face_with_monocle:


It’s actually published by OneSignal, not Bubble - let me know if you still can’t find it.

1 Like

You’re looking for this one - you’ll see it when you go to install a new plugin in your app’s editor!


Aha! I was looking for the By Bubble text. Thanks!

Awesome to see this ship @sam8!

1 Like


So glad I didn’t spend anymore time on this (I’d played with making a good OS plugin on and off for a while, but it kept losing interest)… and hopefully folks can stop thrashing in that “other” thread about OneSignal. Hooray!

1 Like

Interesting. I have an integration already but will take a look. Thanks for the heads up!

Thanks @sam8 and to OneSignal!

Looking forward to trying it. In the manual instructions, why do we have to select “My site is not fully HTTPS”? What’s missing? Thanks.

1 Like

This is amazing @sam8 and @eve! Great job! It works for web apps. However, I’m trying to send push notifications to an Android app (which is a Bubble web app encapsulated with Jasonelle and uploaded to Google Play), and no notifications are received on the same device when using this mobile version of the same Bubble website. The thing is I can see on Bubble logs that the push notification is sent properly to OneSignal plugin. Could it be, @JohnMark, that this is related to the browser not being detected by OneSignal?

Anyway, even if the notification would be delivered, if a user tap on it, he/she would go to the web version rather than to the app version, unless there’s some way to create a deeplink or equivalent O_o

1 Like

@sam8, this is incredible. Thank you and the bubble team for this.

Couple questions.

1.) When I set this up, I got it to prompt me on my safari browser. If I click “do not allow”, is there a way to prompt again, or is it restricted from prompting again? The reason I ask is because I clicked “do not allow” and I could not get it to trigger again, until I used a different browser. If a user declines do they need to reverse course in their browser’s setting? Or is there some way we can ask them to opt in again via our app ?

2.) Are we able to use an expression to retrieve from OneSignal whether the user’s notifications are enabled on their device? I am thinking in regards to conditionals and “only when”.

3.) Can user devices (or test devices) that already were in our OneSignal prior to the plugin install be able to be notified by OS notification in a workflow action? Or does every user need to freshly opt in after the plugin is installed, since there might be a new PID assigned per each device by OS. I hope that makes sense.

Any guidance would be much appreciated.

Hi @marktuff!

  1. Prompting again after rejecting notifications can only be done after a certain amount of time has passed, varying from browser to browser. There are restrictions in place that prevent prompting too frequently on different browsers to reduce spam. If you want to see the prompt again, you can clear history and refresh the page. For simplicity’s sake, we didn’t create an additional opt-in functionality in this first iteration, but if the need is pressing we could consider adding it down the line.

  2. In this iteration of the plugin, you cannot. However, OneSignal notifications fail safely - if you send a notification to a user who has declined permission, it shouldn’t produce an error or problem within your app. Rather, the notification would simply not send. If you need to know whether a particular user is opted in, you can check in the OneSignal dashboard. This, however, is for the one-off check, not something that can be used in a workflow.

  3. Users already in your OneSignal app should be able to receive notifications by filter or segment. However, their Bubble User ID will not be associated with their OneSignal data, so sending notifications directly to them is not feasible unless they opt in again. For existing users, it might be best to use tags to associate their Bubble data with the existing records in OneSignal.

I hope this helps! Please let me know if you have further questions.


Hi @eurogar

I recorded yesterday my ios onesignal thing. Jasonelle will work very well with her. I do not have time to apply it at the moment, but surely in January. There are some configurations! :slight_smile:

OneSignal config:


That’s great news, @JohnMark! :smiley: I see for iOS you need a .p12 file (Production Push Certificate), but for Android you need to configure it with a “Firebase Server Key” and a “Firebase Sender ID”. So I guess Jasonelle would need to be integrated with Firebase to make this work on Android?

1 Like

I don’t think so it’s related with Jasonelle. You simply need to pass the value from your Bubble app to Jasonelle to Android. I’m still fresh in it :wink:

1 Like

What a great xmas present!
Looking forward to try it out soon!

Hi @sam8 thanks for the reply!

Do you know / or can you confirm whether this plugin can also work with web view wrappers that incorporate OneSignal App ID’s, for mobile PUSH notifications? Or is that another can of worms altogether? Thanks!

Hi @sam8, bumping this thread to see if you can respond to my last question :slightly_smiling_face: on whether this is strictly for browsers, and cannot be used for mobile push.

Doble Bumping on Marktuff’s post

1 Like