Integrations

Connected to what you already run

None of this is required. Debut runs the whole onboarding by hand. Connect what you have, and the checklist starts ticking itself.

Not required. Every plan runs the full onboarding without a single connection. Integrations come with the Practice and Firm plans. Each one is optional, connects from Settings in a few minutes, and can be disconnected at any time.

Available now

Three connections you can switch on today.

RMM: NinjaOne

Agent check-ins tick the rollout tasks on their own, and each device is matched to the person who uses it. A person reads as onboarded once their computers report in.

Documentation: Hudu

Each verified credential is filed in Hudu by reference. The secret itself is never stored here. A password changed in Hudu reads as a rotation on the ledger.

Microsoft 365: sign-in and calendars

Your team signs in with Microsoft through your own Entra app. Engineers connect their calendars, bookings land on them, and every session carries a Teams link.

Coming later

On the list, in the order MSPs ask for them. Nothing below is part of a plan yet.

PSA: HaloPSA, ConnectWise, Autotask

HaloPSA can be connected today. What it will do comes later: agreements seeding each plan, and onboarding time and notes written back to the ticket. ConnectWise and Autotask follow.

RMM: Datto RMM, N-able N-central

The same agent check-in tracking NinjaOne has today.

Documentation: IT Glue

Credential and document filing by reference, as with Hudu.

Microsoft 365 people census

The client’s people pulled from their Microsoft tenant instead of a spreadsheet.

Microsoft Bookings

Sessions offered as real bookable slots in Bookings, beside the portal’s own booking.