Integrations

Your ticket system stays yours.

Your team keeps working in its familiar ticket system. octoja delivers monitoring alerts through the appropriate integration.

Overview

What octoja connects to

These systems have their own integrations in octoja. Each detail page explains the available features.

Ticket systems and PSA

Native connectors offer customer import and mapping. cevisio receives events through a dedicated alert channel configured with a URL and API key.

  • TANSS
  • c-entron Service-Board
  • DocBee
  • cevisio
  • HaloPSA
  • Autotask PSA
  • TOPdesk
  • Jira Service Management
  • Freshservice
  • Inserve
  • Odoo
  • Codemeta OS

Alerting

Separate service hours per channel. Into the ticket system during the day, to the on-call engineer at night.

  • Microsoft Teams
  • Email
  • Signed webhooks
  • SMS
  • Voice call
  • App push
  • Internal case

Security

Vulnerabilities and protection status come together in the same dashboard as the rest of your estate — and can be fixed from there.

  • Lywand
  • Bitdefender GravityZone

Documentation and more

Your device inventory is mirrored into the documentation you already keep.

  • Hudu
  • IT Glue
  • woasi
Consistent

What the native ticket connectors provide

This applies to systems such as TANSS, c-entron and DocBee. The cevisio integration sends events by webhook and has its own feature set.

Set up the connection and check availability at any time
Import the customer base from the target system
Map octoja customers onto the structure in the target system
Alerts create tickets, all-clears close them again
Delivery log per message, including resending
In detail

Pages on individual integrations

Your system is not listed? Signed webhooks and the documented REST API connect almost anything. To the open interface

Test the integration against your own system

During trial access we set up the alert channel together and you see whether the ticket arrives the way your dispatch needs it.