Web Help Desk
For a school moving its desk from SolarWinds Web Help Desk to Plugboard. While the connector is on, a repair lodged in Plugboard raises its ticket in Web Help Desk as well, and the Plugboard ticket keeps the link to it; Plugboard can read and close a linked ticket; and the desk’s search can find the tickets still in Web Help Desk. Once the open work is across, turn the connector off.
| Category | Ticketing |
| Authentication | API key |
| Reaches | Your Web Help Desk server, usually internal |
| Needs an agent | Yes, on managed hosting |
| Demo mode | No |
Availability
Section titled “Availability”Limited availability. We set this integration up with your team, starting with a pilot at your school, and check it against your Web Help Desk before you rely on it. It uses Web Help Desk’s REST API, which Web Help Desk 2026.2.1 does not have, so tell us your installed version first: [email protected].
Capabilities
Section titled “Capabilities”ticket.create, ticket.get, ticket.syncStatus, ticket.close,
ticket.search
There is no ticket.comment: notes stay on the Plugboard ticket.
It is not an importer. It does not reach backwards: the tickets already in Web Help Desk stay there. See historical tickets do not migrate.
The private network question
Section titled “The private network question”Web Help Desk is typically an appliance inside the school network.
Self-hosted on that network: reaches it directly.
Managed hosting: needs a connector agent.
Getting the API key
Section titled “Getting the API key”- Sign in to Web Help Desk as an administrator.
- Setup, Techs, Techs, and open the account you want the integration to act as. Create a dedicated one rather than using a person’s.
- On the account, enable API access and generate the API key.
- Copy it.
The key authenticates as that tech, so tickets Plugboard creates are attributed to them.
Configuring it in Plugboard
Section titled “Configuring it in Plugboard”Settings, Connectors, then Web Help Desk under Add a service, and Continue to setup.
Settings
Section titled “Settings”| Field | Value |
|---|---|
baseUrl | Your Web Help Desk base URL, for example https://whd.school.edu |
federatedSearch | Optional. Includes Web Help Desk results in the desk’s search, run as this tech |
Credentials
Section titled “Credentials”| Field | Value |
|---|---|
apiKey | The API key |
Save and test.
Certificates
Section titled “Certificates”Web Help Desk appliances frequently run with a certificate from an internal CA, or a self-signed one.
The server running Plugboard, or the connector agent, has to trust that certificate. Install the CA certificate on that machine. Disabling verification is not offered: an integration that ignores certificate errors on an internal appliance is the path an attacker on the same network would use.
Moving across from Web Help Desk
Section titled “Moving across from Web Help Desk”The same shape as moving across from Zendesk: connect it before cutover so repairs raised in Plugboard appear in Web Help Desk too, carry the open tickets across by hand and close each in Web Help Desk with a note naming the new ticket, then send new requests to Plugboard and turn the connector off on cutover day. Map statuses on the workflow page while it is on.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause |
|---|---|
| Connection refused or a timeout | Internal appliance, and a managed deployment with no agent. Or a firewall between the server and it |
| Certificate error | The machine does not trust the appliance’s CA. Install the CA certificate |
401 | Wrong API key, or API access is not enabled on that tech account |
403 | The tech account lacks permission for the request type or location |
| Tickets create but never close | The account cannot close tickets in that request type |
Related
Section titled “Related”- Moving in, for what else comes across.
- The ticket queue, where the work lands.
- Connector agents, for an appliance on the school network.