K
Device / MDM

Kandji AI Integration

Connect Kandji to BeforeQuery for grounded AI answers and agent actions across Device / MDM.

Connect Kandji
What is it?

About Kandji

Kandji is one of the Device / MDM platforms BeforeQuery connects to. Once linked, the platform's data becomes a first-class source for grounded AI answers and a target for policy-gated agent actions — the same identity, approval, and audit-log guarantees every other integration ships with.

Setup

How to connect Kandji

  1. Step 01

    In the BeforeQuery dashboard, go to Integrations → Device / MDM and select Kandji.

  2. Step 02

    Sign in to Kandji with an account that has permissions to grant BeforeQuery the Device / MDM scopes required.

  3. Step 03

    Confirm the connection. Kandji is now available as a source and action target for every playbook in your workspace.

Explore

Related integrations

A
Addigy

Addigy is one of BeforeQuery's Device / MDM integrations. Connect it once and every agent in your workspace can read, reason over, and act on Addigy data with your policies + audit trail.

AB
Apple Business Manager

Apple Business Manager is one of BeforeQuery's Device / MDM integrations. Connect it once and every agent in your workspace can read, reason over, and act on Apple Business Manager data with your policies + audit trail.

F
Fleet

Fleet is one of BeforeQuery's Device / MDM integrations. Connect it once and every agent in your workspace can read, reason over, and act on Fleet data with your policies + audit trail.

How BeforeQuery uses Kandji

What the agent does with your Kandji connection

  • 01

    Read the Kandji device fleet — hardware, OS, compliance state, assigned user — into the Context Graph.

  • 02

    Push profiles, remote-lock or wipe devices, and enforce compliance rules via Kandji write operations.

  • 03

    Answer employee device questions ("what OS am I on?") + IT questions ("who has an out-of-compliance Mac?").

  • 04

    Coordinate device lifecycle: order, enroll, refresh, wipe, and return — with the right approvals at each step.

Use cases

What teams actually do with the Kandji integration

Lost-device remote lock

Employee reports laptop lost in Slack → BeforeQuery verifies identity, remote-locks the Kandji-enrolled device, invalidates SSO sessions, notifies security. Sub-minute response; full audit trail.

Compliance drift auto-remediation

Nightly, BeforeQuery pulls the Kandji compliance report. Devices in violation (missing OS patch, disabled encryption, expired MDM check-in) get an auto-remediation attempt; user is notified with next steps.

New-hire zero-touch enrollment

HR fires new-hire event → BeforeQuery orders laptop, assigns to user in Kandji, pushes the role-appropriate profile, and pre-configures apps + printers. Device arrives ready; first boot enrolls automatically.

Answer questions grounded in Kandji

Employees and customers ask Kandji-related questions in Slack, Teams, or the widget — BeforeQuery answers with the exact Kandji record shown alongside the response. No context switching, no "log into Device / MDM to check" round-trips.

Kandji — Frequently Asked Questions

Common questions about connecting BeforeQuery to Kandji.

Yes, but with strict approval + step-up MFA. Wipes require security-lead approval, log the reason and target, and cannot be batched. Selective wipe (corporate profile only, keeping personal data on BYOD) is available where Kandji supports it.
Standard OAuth 2.0 where Kandji supports it, otherwise API-key or bearer-token auth. Credentials are stored encrypted at rest (AES-256-GCM) per workspace, never shared across customers, and rotated on request. The connection is scoped to the least-privilege set of scopes each playbook needs — you approve the scope list on install.
No. Your Kandji data feeds only your workspace's own agents and answers. Nothing is used to train a shared model, and nothing crosses workspace boundaries. Bring-your-own-model is available on Enterprise if you want to pin inference to your own OpenAI / Anthropic / self-hosted deployment.
Yes. Every Kandji integration is scoped at install time — you pick which resources, users, or record types are visible. You can further restrict per-playbook: a single playbook only touches the specific Kandji objects it needs. Scope changes take effect on the next sync.
Every write is logged with the acting user, the playbook that fired it, the exact operation, the target entity IDs, and the timestamp — all in the immutable audit log. Writes are rehearsable in simulation mode against a copy of live data before they touch Kandji for real.

Ready to connect Kandji?

Start free. No credit card required. Connect your first integration in under 5 minutes.

Get started free