Integrations

Your ticket system stays yours.

octoja does not bring its own PSA that would have to replace yours. The common German ticket systems are natively connected — with customer import, mapping and a delivery log.

Overview

What octoja connects to

Everything named here has its own integration in the product — no middleware required.

Ticket systems and PSA

Each with its own interface: check the connection, import the customer base, map tenants, delivery log.

  • TANSS
  • c-entron Service-Board
  • DocBee
  • 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
  • WhatsApp
  • App push
  • Internal ticket

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 every ticket system integration brings

No matter which of the 11 systems you run.

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.