STRAX Reach · Alerts and push
Push notifications through Firebase, straight from Reach
Your wallet or airtime app already uses Firebase for push. Reach can send through the same project, so payment confirmations and reminders reach the phone even when the app is closed.
- Android and iOS
- Service account sign-in
- Dead tokens retired
Direct to Firebase with a short-lived token
The credential holds a Firebase service account key. Reach signs a short-lived request with it, exchanges it for an access token at Google and keeps that token until just before it expires, so no long-lived password travels with each notification.
Each message becomes a notification with the subject as title and the text as body, plus the Reach message and conversation ids in the data block so your app can open the right screen. Android gets high priority and iOS the matching urgency header.
Your app registers its registration token as the client's identity, or you send to a topic such as a promotions list. When Firebase says a token is no longer registered, Reach marks the send failed and opts that token out, so the next notice goes to the client's current device.
Where it helps
Payment confirmations
The moment a deposit clears, the client's phone shows the amount and reference.
Top-up reminders
A reminder goes out before a prepaid bundle expires, and the tap opens the top-up screen.
Security prompts
A new-device sign-in triggers a notice asking the client to confirm it was them.
Service notices by topic
A planned maintenance window is announced to everyone subscribed to a status topic.
What you need
-
A Firebase project
The one your mobile app already uses for messaging.
-
A service account key
With the Firebase Cloud Messaging API Admin role, stored in the vault.
-
Token registration
Your app reports its registration token to Reach as the client's identity.
-
Reach Core
Queues the notices and keeps the delivery outcome on the client record.
Good to know
A notice goes to the client's primary device; sending to every device of one client at once is planned. Silent data-only messages are not used yet.
Questions
Do we still need OneSignal?
No other push vendor is required. The OneSignal package remains available for teams that already use it.
What happens when someone uninstalls the app?
Firebase reports the token as unregistered, the send is marked failed with the reason, and the token is opted out.
Can we send to a group of users?
Yes, use an address of the form topic followed by the topic name, and every subscribed device receives it.
Where does the project id come from?
From the service account key file itself, so there is nothing else to configure.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Push via Firebase 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 via Firebase 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 FCM"
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.
Firebase, Android and iOS are trademarks of their owners, 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.


