STRAX Reach · Alerts and push
Push notifications to your app through OneSignal
When your clients use your mobile or web app, Reach can send push notifications through OneSignal and keep a record of each one.
- OneSignal delivery
- Mobile and web apps
- Logged on the record
Notifications that follow the client across devices
Your app logs in to OneSignal with the client's id, and the same id is registered as their push identity in Reach. Reach then sends to that id, and OneSignal delivers to every device the client uses.
The message subject becomes the notification heading and the text its body. Each notification is recorded on the client's conversation so agents know what the client was told.
Push is the cheapest way to tell app users something at once, and it only works if the notification reaches the right person. Using your own client id for the OneSignal login keeps every device of one client together and away from anyone else's.
Notification history is useful evidence when a client disputes that they were told about a fee, a limit change or a suspicious login. Reach keeps that history per person, searchable by your support staff.
Where it helps
Payment received
Tell a client in your wallet app that money has arrived.
Security prompts
Ask a client to review a new device sign-in.
Due-date nudges
Remind app users that a payment is due, with a record of the reminder.
Card controls
Let a client know their card was frozen from the app, and remind them which menu unfreezes it again once they recognise every recent purchase.
What you need
-
A OneSignal app
Connected to your mobile or web app.
-
The REST API key
Entered as the full header value in the OneSignal credential.
-
Client ids in your app
Your app logs in to OneSignal with the id Reach knows the client by.
-
Reach Core
The records the notifications are logged in.
Good to know
Push notifications travel one way. Replies come through the channels where clients can write back, such as chat or email.
Questions
Do we need Firebase or APNs keys in STRAX?
No. OneSignal holds those; Reach only needs the OneSignal app id and key.
Which id should the app use?
Your own client reference or the Reach contact id, registered as the push identity.
What is still missing?
Sending through Firebase or Apple directly, without OneSignal.
Do clients need to opt in?
Mobile platforms ask each user for permission to show notifications. Clients who decline simply have no push identity, and Reach reports the send as failed with that reason.
Can a notification carry a link into the app?
This version sends the heading and text. Deep links into a particular screen are a planned addition that needs a field for the target route.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Push notifications to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 1 |
| Global variable | 1 |
| Workflow | 1 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Push notifications channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - Push"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
OneSignal is a trademark of its owner, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.