# 💬 Push Notifications — Any reliable workaround since Glide removed native support? **URL:** \ **Category:** Ask for Help\ **Tags:** push-notifications\ **Created:** [October 10, 2025, 7:14pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842 "2025-10-10T19:14:44Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Deccatino](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deccatino/32/89505_2.png) [@Deccatino](https://community.glideapps.com/u/Deccatino)\ **Post date:** [October 10, 2025, 7:14pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/1 "2025-10-10T19:14:44Z")
Hey everyone 👋 I wanted to start a discussion around **push notifications** — specifically how others are handling them now that **Glide’s native push feature has been deprecated**. From what I can tell, there isn’t an official replacement yet, but I’ve seen a few people mention possible workarounds using **OneSignal** or **third-party tools like Make (Integromat)**. I haven’t implemented anything myself yet, but I’d really like to explore what’s currently possible. In theory, it seems like it might be achievable with: - A **Make or webhook integration** that sends events to OneSignal’s API - A way to **store device tokens or player IDs** for each user (though I’m not sure if that’s viable with PWAs right now) - Possibly **email or in-app notifications** as temporary alternatives So before diving in, I wanted to ask: - Has anyone successfully set up **OneSignal** or a similar service for Glide apps? - How are you handling **user registration and permissions** for push notifications since the change? - Are there any **confirmed working approaches or partial setups** that others could learn from? Right now, my app has **zero push functionality** , and I’m just trying to find a direction that could realistically work long-term. If anyone has experience or insights to share — even if it’s just partial progress — it’d be great to collaborate on documenting a community workaround. Thanks in advance to anyone who can shed light on this — it feels like a lot of us are in the same spot. — Declan ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [October 11, 2025, 1:41am UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/2 "2025-10-11T01:41:41Z")
Have you seen the below? > [@megaphone Glide Push Notifications (2025 Tutorial)](https://community.glideapps.com/t/glide-push-notifications-2025-tutorial/82936): > > [[How To Add Push Notifications To Glide Apps Fast!] ](https://www.youtube.com/watch?v=0UnlDAmOlDM) What’s Up Gliders! In this video, I walk you through the process of setting up push notifications for your Glide App using OneSignal. We start by creating a free account on Netlify and uploading two essential files to spin up a “mini website”. Then, I guide you through configuring OneSignal, including creating a new app and customising the push prompt. Finally, I demonstrate how to set up the necessary columns in Glide to manage u… ---
**Author:** ![Deccatino](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deccatino/32/89505_2.png) [@Deccatino](https://community.glideapps.com/u/Deccatino)\ **Post date:** [October 11, 2025, 7:41am UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/3 "2025-10-11T07:41:16Z")
Thanks for sharing! I’ve actually seen that video — and working through that exact method is what prompted me to start this topic. I’ve managed to get the base setup working, but I’m struggling to figure out how to send different push notifications for various events across the app — things like new messages, order updates, or community replies. I understand the general flow using OneSignal, but I’m not sure how to structure the logic or payloads so each event triggers its own unique notification. Any insight or examples on handling multiple notification types would be massively appreciated. 🙏 ---
**Author:** ![Laurence\_Schuberth](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/laurence_schuberth/32/65729_2.png) [@Laurence\_Schuberth](https://community.glideapps.com/u/Laurence_Schuberth)\ **Post date:** [October 13, 2025, 8:04am UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/4 "2025-10-13T08:04:20Z")
I am DESPERATE for push, I tried this video as well, and go everything set up as shown, but I could never get it to work reliably at all. I did request help from the video creator, but heard nothing, so I abandoned ship, but any ideas would be great. ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [October 13, 2025, 4:55pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/5 "2025-10-13T16:55:19Z")
I am trying as well, getting 400 errors from the call API. I’ll try again tonight and let you know! ---
**Author:** ![Deccatino](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deccatino/32/89505_2.png) [@Deccatino](https://community.glideapps.com/u/Deccatino)\ **Post date:** [October 13, 2025, 5:21pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/6 "2025-10-13T17:21:10Z")
Hey guys 👋 Just a quick update — I’m currently testing a **Glide → OneSignal → Make** workflow to handle **multiple different push notifications** across various user actions. Still in early testing, but it’s looking promising so far. I’ll share my findings (and setup steps if it works reliably) once I’ve got everything stable — hopefully this can help anyone else struggling with push setups too 👍 ---
**Author:** ![Laurence\_Schuberth](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/laurence_schuberth/32/65729_2.png) [@Laurence\_Schuberth](https://community.glideapps.com/u/Laurence_Schuberth)\ **Post date:** [October 13, 2025, 7:07pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/7 "2025-10-13T19:07:55Z")
Hey, thank you so much, my clients are absolutely desperate for some kind of notifications as most other app builders offer that feature, but I am Glide through and through because I think it’s the best so I’m stuck ---
**Author:** ![Laurence\_Schuberth](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/laurence_schuberth/32/65729_2.png) [@Laurence\_Schuberth](https://community.glideapps.com/u/Laurence_Schuberth)\ **Post date:** [October 13, 2025, 7:08pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/8 "2025-10-13T19:08:44Z")
@Deccatino oh if you could get it working, you will make my year !!! 😀 ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [October 14, 2025, 3:30pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/9 "2025-10-14T15:30:38Z")
Hey, I replied to you in this post: > [@megaphone Glide Push Notifications (2025 Tutorial)](https://community.glideapps.com/t/glide-push-notifications-2025-tutorial/82936/6): > > This is reply for another post that concerns this actual thread. @Laurence_Schuberth Ok, first thing, I found out that by adding “Included\_segments”, the call doesn’t fail anymore. { "app\_id": "appid", "target\_channel": "push", "headings": { "en": "{{header}}" }, "contents": { "en": "{{contents}}" }, "included\_segments": ["All"], "includes\_aliases": { "external\_id": {{emails}} } } Secondly, OneSignal doesn’t allow you to setup external ID anymore from the clien… ---
**Author:** ![Deccatino](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deccatino/32/89505_2.png) [@Deccatino](https://community.glideapps.com/u/Deccatino)\ **Post date:** [October 28, 2025, 9:52pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/10 "2025-10-28T21:52:19Z")
**Update from me 👋** Quick update now that we’ve got a working first-party push notification setup running with Glide. ✅ **What’s working well** - **Android & desktop:** flawless — notifications appear instantly and behave like native ones. - **Branding:** fully ours — only the small **Chrome logo** remains; all other icons and badges are customised. - **Stack:** first-party **service worker** hosted on **Netlify** , connected to **Make** for event triggers and delivery. ⚠ **iOS caveat** - Users still need to **add the Netlify web app to their Home Screen** to enable notifications. Once added, everything works perfectly — but it does mean iOS users effectively have **two apps** (the main app and the push-enabled one). 💡 **How we approached it (high level)** - No OneSignal or third-party dashboards — everything runs through our own infrastructure. - Each event, key, and trigger is configured manually through Make, giving us full control and flexibility. - You can also build an **admin dashboard** to send system or group notifications. 🔒 **Security & privacy** We’ve put a big focus on keeping the system safe and transparent: - All requests are handled through **secure HTTPS endpoints** hosted on Netlify. - User identifiers are **tokenised** — no personal data is ever stored in plain text. - Device registration keys are unique per user and used **only** for sending app notifications. - No data is shared externally — everything stays within the Glide, Make, and Netlify ecosystem. - The system can be expanded with authentication keys or access rules if needed for larger deployments. 📈 **Heads-up on Glide updates** - During testing, this setup **burned through a fair few Glide updates** (lots of webhooks, writes, and recalcs). - Once the build is stable, I’ll monitor usage more closely and share some stats on what’s manageable. - For anyone testing, I’d suggest throttling Make polling and batching webhook actions during development. 🚧 **Still building** - Android and desktop are running beautifully. - We’re still refining iOS handling, automation structure, and some internal workflows — updates will follow as we continue to test and optimise. If you’re exploring similar setups, drop your findings — would be great to share notes and shape a proper community workaround together. — Declan ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [October 28, 2025, 11:24pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/11 "2025-10-28T23:24:40Z")
> [@Deccatino](#): > > Users still need to **add the Netlify web app to their Home Screen** to enable notifications. Yeah, unfortunately, this is how Apple deal with PWA push notifications now. ---
**Author:** ![Deccatino](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deccatino/32/89505_2.png) [@Deccatino](https://community.glideapps.com/u/Deccatino)\ **Post date:** [October 28, 2025, 11:44pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/12 "2025-10-28T23:44:22Z")
yeah, that’s what I’ve found too. One theory I’ve been exploring is to make the push setup part of the onboarding process on the Netlify-hosted version. The idea would be: users install that version first (so their device gets registered and subscribed properly), and then — once that’s done — we automatically redirect them to the main app. In theory, that could result in just one installed version that’s already subscribed, instead of users ending up with two separate apps. We could then manage a superficial notifications toggle inside Glide — letting users turn notifications on or off within the app UI without actually unsubscribing the device. That would keep the subscription intact while still giving users the sense of control. That said, I’m not entirely sure on the legality or compliance side of that approach yet — especially around consent and data handling — so it’s just a working theory for now. ---
**Author:** ![MJolley](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mjolley/32/85220_2.png) [@MJolley](https://community.glideapps.com/u/MJolley)\ **Post date:** [January 14, 2026, 9:01pm UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/13 "2026-01-14T21:01:41Z")
I know this is an old discussion, but I’m trying to get this working in my app right now and running into issues. But, separately, I was wondering: is there a way to create an HTML object/code bit within a Glide app that gets called for OneSignal instead of Netlify? Then the user only has to install the Glide app for it to work. ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [January 15, 2026, 3:47am UTC](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/14 "2026-01-15T03:47:33Z")
The HTML needs to contain the script tag from OneSignal on the page. Glide doesn’t allow this except in embed component. So unfortunately, you need an external hosted HTML page. You could try with GitHub page.