STRAX Reach · Alerts and push
Raise Opsgenie alerts from client conversations
When clients report that payments are failing, the right engineers should know at once. Reach creates an Opsgenie alert for the responsible team from the conversation itself.
- Alert API
- Team routing
- Conversation reference
Alerts addressed to a team by name
Each escalation contact in Reach carries an Opsgenie team name as its address. Queue a message to that contact and Reach creates an alert with the subject as the alert message, the text as its description and the team as responder.
The alias is built from the Reach message id, so a retried send updates the same alert. Priority and source are settings per environment, which keeps staging tests at a low priority on a quiet schedule.
Details carry the contact and conversation references, so the responder can open the full client thread in Reach while the alert is still ringing.
Atlassian has stopped selling Opsgenie and plans to end support in April 2027, with Jira Service Management taking over on-call alerting. The API base is a setting, which leaves room to move when your team migrates.
Where it helps
Card switch outages
Alert the payments team when agents see several clients reporting declined cards within a short window.
Messaging provider trouble
Page the platform team when an SMS or WhatsApp provider starts refusing messages.
Account takeover reports
Send a high-priority alert to the security team when a client reports that someone else changed their banking details.
What you need
-
An Opsgenie API integration
With create access, and its key stored in the STRAX credential vault.
-
Team names
The Opsgenie team to alert for each escalation contact.
-
Priority and source
Chosen per environment in the Reach settings.
-
Reach Core
Where escalations are queued and logged beside the client conversation.
Good to know
This channel only creates alerts. Acknowledgements, notes and closing happen in Opsgenie and are not written back to the conversation yet.
Questions
How do we alert different teams?
Create one escalation contact per team with the team name as its Opsgenie address. A contact addressed as default leaves routing to the integration.
Which data centre do we point at?
The EU host for accounts in Europe and the default host otherwise, set once in the Reach settings.
Will a retry page twice?
No second alert is created. The alias from the Reach message id makes a retry update the alert it already created.
What about the Opsgenie retirement?
Plan the move to Jira Service Management with your operations team. Its alert API takes the same fields, and the README describes the change.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Opsgenie 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 | 3 |
| Workflow | 1 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Opsgenie 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 - Opsgenie"
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.
Opsgenie, Atlassian and Jira Service Management 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.