Hey everyone :waving_hand: 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

Have you seen the below? [image] megaphone Glide Push Notifications (2025 Tutorial) Community Resources [How To Add Push Notifications To Glide Apps Fast!] 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…

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. :folded_hands:

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.

I am trying as well, getting 400 errors from the call API. I’ll try again tonight and let you know!

Hey guys :waving_hand: 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 :+1:

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

@Deccatino oh if you could get it working, you will make my year !!! :grinning_face:

Hey, I replied to you in this post: [image] megaphone Glide Push Notifications (2025 Tutorial) Community Resources 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…

Update from me :waving_hand: Quick update now that we’ve got a working first-party push notification setup running with Glide. :white_check_mark: 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. :warning: 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). :light_bulb: 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. :locked: 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. :chart_increasing: 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. :construction: 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

[image] 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.

💬 Push Notifications — Any reliable workaround since Glide removed native support?

Ask for Help

Darren_Murphy October 11, 2025, 1:41am 2

Have you seen the below?

Topic		Replies	Views
Are there any alternative push notifications? Ask for Help	10	1607	February 1, 2023
Chat Alerts and notifications Ask for Help	1	83	December 7, 2025
Push Notifications, gone? Ask for Help	7	300	February 21, 2025
Newbie questions Ask for Help	19	1322	May 21, 2021
Cant find push notification Ask for Help	5	170	February 11, 2025

💬 Push Notifications — Any reliable workaround since Glide removed native support?

Related topics