Operational notifications · Matrix · connected laboratory records
Send FlaskTrack laboratory events to Matrix without moving the system of record
Use Matrix Hookshot to deliver FlaskTrack notifications into the room where your team coordinates laboratory work.
Chat remains the notification surface while FlaskTrack retains the authoritative laboratory record and the operational context behind it.
What you need
Matrix Hookshot
The Matrix environment must provide a working Hookshot deployment with generic
inbound webhooks enabled.
A destination room
Choose the room that should receive alerts and invite the Hookshot bot if
needed.
Room permissions
The bot must be able to send state events, commonly requiring moderator-level
power.
FlaskTrack administrator access
An organization administrator manages the Matrix provider configuration.
Matrix Hookshot setup instructions
- 1. Confirm generic webhooks are available. Your Matrix administrator must enable Hookshot's generic webhook service and expose its listener through a public URL.
- 2. Open the destination room. Choose the Matrix room that should receive FlaskTrack notifications.
- 3. Invite the Hookshot bot. Invite it if it is not already present.
- 4. Grant the required room power. Ensure the bot can send state events; Hookshot documents Moderator as the usual level.
- 5. Create an inbound webhook. Send
!hookshot webhook flasktrackin the room. - 6. Copy the URL returned by Hookshot. Treat the unique room webhook URL as a secret.
- 7. Open FlaskTrack notification providers. Go to organization settings and open Notification Providers.
- 8. Add the Matrix provider. Select Matrix and paste the complete Hookshot URL. Optionally record the room alias or room ID.
- 9. Save and test. Confirm the test notification appears in the intended Matrix room.
- 10. Enable operational delivery. Disable or remove the provider when the room connection is retired.
For self-hosted Matrix administrators
Enable the generic service
Configure Hookshot's generic integration service, public URL prefix, and webhook
listener.
Expose the correct listener path
Current Hookshot documentation recommends
/webhook; the older root
path
is deprecated.
Configure service permissions
Allow the relevant users, homeserver domain, or room to use the generic
service.
Accept JSON payloads
Hookshot supports JSON and uses a
text field as the message body
when
provided.
Security and troubleshooting
- Protect the unique Hookshot URL and replace the connection if it is exposed.
- Confirm the Hookshot bot remains in the destination room.
- Confirm the bot can send messages and state events.
- Confirm the inbound webhook connection still exists.
- Confirm the Hookshot listener and public URL remain reachable.
- Confirm the FlaskTrack provider is enabled.
- Use Send test after every Hookshot, proxy, room, or provider change.