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

Ask for Help
1

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

1 Like
2

Have you seen the below?

2 Likes
3

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:

1 Like
4

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.

5

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

1 Like
6

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:

1 Like
7

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

8

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