ImmyBot
Deployment automation you can interrogate.
ImmyBot is the machinery under your software estate — deployments, maintenance sessions, and the schedule that runs while everyone is asleep. Connect your instance and a session can read all of it: which tenants and computers it manages, what's deployed where, which maintenance sessions failed and why, and what's queued to happen next. The connection is read-only in the structure of the code, not as a setting — there is no way to start a deployment, edit a task, or touch an endpoint from here.
The story
What changes once it’s connected.
When an ImmyBot deployment goes wrong you find out the same way every time: by scrolling session logs at eight in the morning. Connected, the question is asked once instead — which deployments failed this week and why, what version of an app is actually deployed at a given client, which computers are stale or stuck in onboarding, and what tonight's maintenance window is going to touch before it touches it.
The coverage follows how ImmyBot is really structured. Tenants — the customer orgs it deploys into — with agent online/offline status as the first call for 'is anything down'. The computer roster with per-machine detail, sessions and primary person. Both software catalogs: the global one ImmyBot maintains and the local one your instance defines. Maintenance at both depths — the sessions that ran (the execution log) and the task library they ran from. And provider links: the RMM and PSA integrations your instance sits on top of, with their client mappings, which is the join key when a session cross-references ImmyBot against Automate or PSA data.
One honest edge worth knowing: the setup is the heaviest of the group, and we'd rather say so. Authentication is an Entra app registration using client credentials, and ImmyBot only accepts the token after a person mapping inside ImmyBot itself — the connect page walks through all of it, including the one step that bites everyone (the Enterprise App object ID, not the app registration's). Ten minutes with the walkthrough, and the connector verifies both stages live before saving anything.
Things you can ask
Ask it like you’d ask a teammate.
Skills included
Every skill, in the open.
9 skills across 5 areas
Read-only, structurally: every skill is typed as a read, the MCP boundary re-checks read scope before a call runs, and no write path exists in the client. Nothing here starts or cancels a deployment, edits a maintenance task, changes a schedule, onboards a computer, or sends anything to an endpoint. The credential is your own Entra app mapped to an ImmyBot user, so everything the agent reads is attributed to that user in ImmyBot's own audit trail, and a session sees exactly what that user can see.
Tenants & agent health2The shape of the instance: which customer tenants ImmyBot manages, and live agent online/offline status — the first call for 'is anything down'.⊘ Reading only — no tenant is created, renamed, or relinked from here.›
list_tenantsList the customer tenants, with filtering and paging.get_agent_statusAgent online/offline rows, instance-wide or for one tenant.
Computers2The device roster ImmyBot deploys to, from fleet sweeps down to one machine's full detail.⊘ Reading only — no computer is onboarded, reassigned, or sent anything. Stale/onboarding flags are triage filters, not actions.›
list_computersPage through computers — filter by name/user, tenant, stale, or onboarding.get_computerOne computer in full, optionally with its sessions and primary person.
Software catalogs2What ImmyBot can deploy: the global catalog it maintains and the local entries your instance defines.⊘ Reading only — nothing is added to either catalog, and no deployment is triggered.›
list_software_globalThe ImmyBot-maintained global software catalog.list_software_localYour instance's own software entries.
Maintenance & tasks2The execution story: maintenance sessions that ran (and failed), and the task library they were built from.⊘ Reading only — no session is started, retried, or cancelled, and no task is edited. Session queries go through ImmyBot's grid endpoint, so very exotic filters are probed rather than assumed.›
list_maintenance_sessionsMaintenance sessions (execution runs), filterable by computer or tenant.search_maintenance_tasksSearch the maintenance task library, global or local.
Provider links1The RMM/PSA integrations your instance sits on top of, with client mappings — the join key for cross-referencing against Automate or PSA.⊘ Reading only — no provider is linked, unlinked, or remapped.›
list_provider_linksProvider integrations and, optionally, their client mappings.
Connecting
Wire it in, in an afternoon.
How to connect
- 01Register a single-tenant app for ImmyBot in Microsoft Entra (client credentials) and create a secret.
- 02In ImmyBot, map the app's Enterprise App object ID to a Person (AD External ID) with an Admin user.
- 03Enter your instance URL and the three Entra values on the connect page — it verifies both auth stages live before saving.
Patch your stack in.
Start the Switchboard free trial against your own environment — read-only, traced answers, live in an afternoon. The apps are on the shelf when you want them.