Skip to content
plugboard.appRequest a demo

Connectors

How connectors work

Every integration in Plugboard is a connector. The application never depends on Jamf, or Synergetic, or Zendesk. It depends on a capability, and a connector declares which capabilities it implements.

That is why a school running Intune and one running Jamf use the same repairs screen, and why swapping an MDM is a configuration change rather than a project.

Capability. A named operation the platform can ask for: device.lookupBySerial, sis.getRoster, email.send. Full list in capabilities.

Connector. A definition: a category, an authentication kind, a configuration form, a secret form, and the capabilities it implements.

Connector instance. A connector you have configured, with your URL and your credentials.

When a feature needs something done it asks for a capability. The platform finds an enabled instance implementing it and calls the handler. If there is no such instance, the feature says so plainly rather than failing obscurely.

The guides below cover common integrations. The generated connector reference lists every registered provider and distinguishes live handlers, demo workflows, blocked actions and unsupported contracts. A registered handler alone is not a promise that an operation works in live mode or is available in your deployed release.

Add a service on Settings, Connectors lists services by setup priority. Core identity, device and student systems come before supporting integrations, and every provider sits in its own family. The guides below are grouped for reference.

  • Q-SYS, PJLink, Crestron XiO Cloud and Zoom Rooms provide read-only monitoring. Hardware and vendor-account pilots are required before production rollout. There is no Extron or Teams Rooms connector.
  • TeamViewer adds device status through explicit mappings to existing remote support targets; it does not create or control a remote session.
  • Xero and MYOB support reviewed purchasing exports after authorization, account/tax mapping and the required approvals.
  • Microsoft 365 and Google calendars, Teams Workflows and Google Chat extend the existing directory connections with explicit work-item publishing.

See School operations for the supported operations, setup requirements and provider limits, and Remote support for TeamViewer status.

ConnectorAuthNotes
Jamf ProOAuth client credentialsThe most capable. Supports smart group pull for loan pools
Microsoft IntuneOAuth client credentialsVia Microsoft Graph
KandjiAPI token
MosyleAPI tokenManager and Business. Common in Apple-heavy schools
Chrome EnterpriseService accountChromebooks, via the Google Admin SDK
Mock MDMAnyFor demos and tests
ConnectorAuthNotes
SynergeticBridge bearer keyCommon in independent schools. Through a REST bridge the school runs, usually on a private network
SentralAPI key plus tenant keyWidespread in New South Wales
Compass EducationService account credentialsDominant in Victoria
OneRosterOAuth 2 client credentialsRead-only 1.1/1.2 roster; school-provider validation required
WondeSchool tokenRead only, one school per token, through Wonde. Limited availability
ConnectorAuthNotes
LDAP and Active DirectoryBind accountAuthenticate, look up, reset passwords. Reaches a private network
Directory managementProvider-dependentLegacy directory actions use demo data. Live identity support varies by provider; see the generated reference
ConnectorAuthNotes
SMTPUsername and passwordAny SMTP server. The simplest option
Google WorkspaceService accountSends via the Gmail API with delegation
Console emailNoneLogs instead of sending. Development only
TwilioAccount SID and auth tokenSMS
ConnectorAuthNotes
ZendeskAPI tokenCreate, comment on and close tickets
Web Help DeskAPI keySolarWinds. Reaches a private network
ServiceDesk Plus CloudZoho Self Client refresh tokenRequests in one portal, for a school moving its desk across. Limited availability
FreshserviceAPI keyTickets in one workspace. Limited availability
Jira Service Management CloudOAuth 2.0 (3LO) appCustomer requests in one service desk. Limited availability
ConnectorAuthNotes
Apple GSXAPI tokenWarranty and AppleCare coverage
Dell warrantyClient credentialsEntitlement by service tag
CompNowAPI tokenLodge external repairs and sync status
EdunetOAuth client credentialsLodge repairs as service jobs, send notes and photos, and sync status
ConnectorAuthNotes
Printers over SNMPSNMP community stringToner, status and errors. Reaches a private network
PaperCutAuth tokenBalances, page counts, and writing the tap card. Reaches a private network
ConnectorCategoryNotes
ThreatLockerSecurityEndpoint allowlisting approvals
SalesforceCRMAccounts, contacts and cases
Google SheetsSpreadsheetInduction roster import
OllamaAIA separately configured local model; container deployments can use a sidecar
AnthropicAIClaude, on your own key
OpenAI-compatibleAIAny OpenAI-style endpoint, hosted or your own GPU box

More than one MDM. You can configure several, and a device resolves through whichever one knows it, which is what a mixed fleet needs: Jamf for Macs, Intune for Windows, Chrome Enterprise for Chromebooks.

More than one SIS. Unusual, but supported. Rosters merge and people are de-duplicated.

Email. Pick one. SMTP is simpler and works with anything. Google Workspace sends as a real mailbox in your domain, which some schools prefer for deliverability.

Ticketing. If you already run Zendesk or Web Help Desk, connect it and switch off the built-in module.tickets. Running both queues means work gets lost between them.

Core includes three connectors. Standard and above are unlimited.

Adding one past the limit is refused, and tells you what to do about it. Nothing already configured is ever touched: reconfiguring an existing connector is always allowed, and deployments licensed before the cap existed stay uncapped.

Connectors installed on first run, meaning the bundled AI model and vendor-hosted AI, do not count against your allowance.

Settings, Licence & billing shows connectors used against the limit.

Most connectors have a demo mode that returns realistic fictional data instead of calling the real system.

Turn it on to see a feature work before credentials arrive, then turn it off. Leaving it on in production is the most common configuration mistake in the product. The compliance page counts connectors still in demo mode, so it gets noticed.

Some connectors talk to something that normally lives inside a school network: Active Directory, a Synergetic REST bridge, PaperCut, a printer answering SNMP, Web Help Desk.

A self-hosted install on that network reaches them directly and needs nothing extra.

A managed deployment cannot, and uses a connector agent: a small program installed inside your network which dials out, collects queued work and returns results. No inbound firewall rule.

Whether an agent is needed depends on where the deployment runs, not on the connector.

Connector credentials are protected with envelope encryption. They are encrypted before they reach the database and decrypted in memory only for the duration of a call. A connector handler never gets database access; it returns data and the platform decides what to persist.

The master key is SECRETS_MASTER_KEY. See secrets and keys.