# 📣 Glide Push Notifications (2025 Tutorial)

**URL:** <https://community.glideapps.com/t/glide-push-notifications-2025-tutorial/82936>\
**Category:** Community Resources\
**Tags:** push-notifications, tutorial\
**Created:** [July 4, 2025, 9:43am UTC](https://community.glideapps.com/t/glide-push-notifications-2025-tutorial/82936 "2025-07-04T09:43:43Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**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:25pm UTC](https://community.glideapps.com/t/glide-push-notifications-2025-tutorial/82936/6 "2025-10-14T15:25:10Z")

</div>

This is reply for another post that concerns this actual thread.

> [@speech\_balloon Push Notifications — Any reliable workaround since Glide removed native support?](https://community.glideapps.com/t/push-notifications-any-reliable-workaround-since-glide-removed-native-support/84842/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

@Laurence_Schuberth

Ok, first thing, I found out that by adding “Included\_segments”, the call doesn’t fail anymore.

```json
{
  "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 client. You need to use the API to do so. But I found a workaround.  
In the index.html file of the netlify app, replace the addAlias line:

```js
//OneSignal.User.addAlias("external_id", externalID);
OneSignal.User.addAlias("user_id", externalID);

```

By doing this, you will still be able to interact with the _[View user](https://documentation.onesignal.com/reference/view-user)_ API route from OneSignal by refering the alias label as user\_id:

```auto
https://api.onesignal.com/apps/{app_id}/users/by/{alias_label}/{alias_id}
Replace {app_id} by the app id of OneSignal
Replace {alias_label} by "user_id"
Replace {alias_id} by the email.

```

And good news, It also works with includes\_aliases! So you can replace the code for the call API with this one:

```json
{
  "app_id": "appid",
  "target_channel": "push",
  "headings": {
    "en": "{{header}}"
  },
  "contents": {
    "en": "{{contents}}"
  },
  "included_segments": ["All"],
  "includes_aliases": {
    "user_id": {{emails}} // <=== "external_id" replaced with "user_id"
  }
}

```

It is now working perfectly fine for me!

Don’t hesitate to ping me if you need further help!

---

_[View the full topic](https://community.glideapps.com/t/glide-push-notifications-2025-tutorial/82936)._