Nanoheal is included in the 2026 Gartner® Magic Quadrant™ for Digital Employee Experience Management Tools.In the 2026 Gartner® Magic Quadrant™ for DEX tools. See it on Gartner ↗

NanohealNanoheal
Schedule a demo

Orchestrate the IT Ecosystem

One fix can reach the laptop, the directory and the ticket.

Most fixes don’t end on the laptop, and connecting each system is usually a project of its own. Connect your service desk, directory and chat tools once. After that, a fix can finish in any of them, under the same approvals as an action on the laptop.

Schedule a demo

One event, four systems

Connected once, per site

Ticket events in, directory actions out, and any system with a standard API, described rather than built.

Event 20227
VPN connection failed · LT‑2207

  1. Ticket events

    Your ITSM → Nanoheal

    Taking in inbound ticket events from your ITSM, to show what to fix next and which calls stopped.

    ✓ticket closed with the record

  2. API and catalogue

    Your tools → Nanoheal

    Access through a REST API with site-scoped API keys, read or write.

    ✓licence reclaimed

  3. Connectors

    Nanoheal → your tools

    Per-site connections to ServiceNow, BMC Helix, Autotask, Microsoft Teams and Slack.

    ✓entry corrected

  4. Event subscriptions

    Nanoheal → any URL

    Device and fix events, through webhooks and event subscriptions to any URL.

    ✓team notified

How it connects

A connector per site, not a project per system.

Connections are scoped to a site, so one console can hold a regional desk, a division’s own instance and a client’s PSA without choosing between them.

Nanoheal console: ecosystem connectors
Nanoheal console · Connectors

Actions in other systems run through outbound integrations, with APIs and MCP servers as no-code building blocks. Ask us which are live for your stack

Around the endpoint

The directory, the service desk and Teams finish the job.

A forgotten password or a new starter needs more than the laptop: a password to reset, a ticket to close, a person to tell.

0:000:010:020:030:040:05 DeviceDirectoryService deskTeams Sign-in failures detected Password reset Cached credentials refreshed Ticket closed User told they’re back in

Swipe to see the whole run →

ITSM

Service desk.

Ticket history gives the problem its context, and the ticket is updated when the fix completes, by the platform rather than a person. Assisted IT, where the desk runs the approved fix, starts straight from the ticket.

Identity

Directory.

Password resets on the device, through Active Directory and Entra ID.

Collaboration

Teams and channels.

Notify the right people when a fix needs a human, through Microsoft Teams and Slack. The device details go with the message, so whoever picks it up starts with the facts.

What governs it

Acting in a directory is higher stakes than acting on a laptop.

Credentials
Held per site, with secrets never returned to the console.
Keys
Scoped to a site and to read or write. Only a hash of each key is stored.
Access
Who configures a connection, and who runs what through it, is set with role-based access and MFA.
Connections · Site: Acme EU
4 connectionsCredentials held per site · keys stored as hashes
  • Ticket events

    ITSM → Nanoheal

    1,912 events this week Receiving
  • REST API

    Your tools → Nanoheal

    3 keys · 2 read, 1 write Active
  • Connector

    Nanoheal → collaboration

    Notify when a fix needs a person Active
  • Event subscription

    Nanoheal → any URL

    fix.completed · fix.failed Paused

Configuration changes land in the same audit log as every fix. Trust & security.

A fix is done when the laptop works, the ticket is closed and the person knows.

Read next