Integrations & API
Ticketing systems, alerting with on-call rota, webhooks and an open API.
What octoja connects to — and how the alert arrives
A platform that demands every other tool make way never gets adopted. That is why octoja fits into your existing landscape.
Ticketing and PSA systems: DocBee, TANSS, TOPdesk, c-entron, HaloPSA, Autotask, Jira Service Management, Freshservice, Inserve, Odoo and others
Documentation: Hudu, IT Glue, woasi
Security: Bitdefender GravityZone and Lywand vulnerability audit
Alerting via Microsoft Teams, email, signed webhooks as well as SMS, phone call, WhatsApp and app push
Notification groups with their own service hours per channel — into the ticketing system during the day, by phone call to the on-call engineer at night, with days and times freely configurable, including across midnight
Escalation based on failure rate rather than every blip: an alert only once a defined proportion of recent checks fails — by count or period, above a minimum severity
Alerts raised outside service hours are held back and delivered in the next window rather than being lost; all-clear messages always go through immediately
An alert latch per channel prevents alert floods, and on all-clear the ticket in the external system closes automatically
MCP server with graduated permissions so AI assistants can access the estate under control
Documented REST API with an open Swagger interface
How this plays out in different environments
The same area means something different to a service provider than it does to a hospital.
Judge it against your own estate
With trial access you see this area with your devices rather than with demo data.