Skip to content
plugboard.appRequest a demo

Connectors

ServiceDesk Plus Cloud

For a school moving its desk from ServiceDesk Plus Cloud to Plugboard. Open requests stay linked to their Plugboard tickets during the switch-over: a linked ticket carries Open in ServiceDesk Plus, and Plugboard reads each request’s status. It is a request connector for one portal, not two-way synchronisation.

CategoryTicketing
AuthenticationThe school’s own Zoho Self Client and refresh token
ReachesThe data centre’s service domain and accounts server, from a fixed table
Needs an agentNo
Demo modeNo

Limited availability. We set this integration up with your team, starting with a pilot at your school, and check it with the provider before you rely on it.

ticket.create, ticket.get, ticket.syncStatus, ticket.comment, ticket.close

  • Raise a request, with the subject (up to 250 characters), the description as plain text, and the request template and site when set. The requester is the technician account the token belongs to; Plugboard people are not mapped to ServiceDesk Plus requesters.
  • Read a request and its status. Only the ID, subject and status name are kept. Open, On Hold, Resolved, Closed and Cancelled map to Plugboard statuses; any other status keeps its own name.
  • Add a note. Notes are private unless the note is sent as public. They never notify technicians, never count as a first response and never copy to linked requests. ServiceDesk Plus must confirm the visibility that was sent.
  • Close a request, by setting the Closed status with the closure comment “Closed from Plugboard” and the closure code when set. A second read must show the request closed.

No attachments, search, webhooks, field mapping, requester sync or deletion.

The school registers its own OAuth client. Plugboard registers no Zoho client and hosts no sign-in callback.

  1. Make a technician account kept for Plugboard, with a role that covers only requests, on the site Plugboard should use.

  2. Signed in as that technician, open the Zoho API console for the school’s data centre (for Australia, https://api-console.zoho.com.au), add a Self Client, and copy its client ID and client secret.

  3. In the Self Client’s Generate Code tab, enter exactly these scopes and no others: SDPOnDemand.requests.CREATE,SDPOnDemand.requests.READ,SDPOnDemand.requests.UPDATE

  4. Exchange the grant code for a refresh token before it expires, against the same data centre’s accounts server, with the values in the request body:

    Terminal
    curl -sS https://accounts.zoho.com.au/oauth/v2/token \
    --data-urlencode grant_type=authorization_code \
    --data-urlencode client_id=<client id> \
    --data-urlencode client_secret=<client secret> \
    --data-urlencode code=<grant code>

    Keep the refresh_token from the reply.

Zoho keeps at most 20 refresh tokens per user and client. Generating more for the same technician and Self Client stops the oldest, which may be Plugboard’s; the connection test then reports a sign-in failure.

Settings, Connectors, then ServiceDesk Plus Cloud under Add a service, and Continue to setup.

FieldValue
dataCentreThe data centre the account is in. au unless you know otherwise
portalThe part after /app/ in your ServiceDesk Plus address
clientIdThe Self Client’s client ID
siteIdFor a portal with several sites: the one site Plugboard works in
templateIdThe request template for requests Plugboard raises, when the portal needs one
closureCodeThe closure code name, when the portal needs one to close a request
allowWritesOff by default. Turn it on only when Plugboard should raise, note and close requests
FieldValue
clientSecretThe Self Client’s client secret
refreshTokenThe refresh token from step 4

Both are sealed like every connector credential. The connection test reads one request and, with siteId set, fails when the technician can see requests in another site.

Every address comes from the data centre. There is no URL field, so a custom domain such as help.school.edu.au cannot be used: the fixed service domain reaches the same portal.

Data centreService domainAccounts server
auhttps://servicedeskplus.net.auhttps://accounts.zoho.com.au
ushttps://sdpondemand.manageengine.comhttps://accounts.zoho.com
euhttps://sdpondemand.manageengine.euhttps://accounts.zoho.eu
inhttps://sdpondemand.manageengine.inhttps://accounts.zoho.in
ukhttps://servicedeskplus.ukhttps://accounts.zoho.uk
cahttps://servicedeskplus.cahttps://accounts.zohocloud.ca
jphttps://servicedeskplus.jphttps://accounts.zoho.jp
sahttps://servicedeskplus.sahttps://accounts.zoho.sa
cnhttps://servicedeskplus.cnhttps://accounts.zoho.com.cn
  • Nothing is written unless allowWrites is on.
  • A note or close reads the request first. With siteId set, a request in another site is refused before anything is written.
  • Raising a request and adding a note are never retried automatically. A write ServiceDesk Plus does not confirm fails with “Check the request in ServiceDesk Plus before trying again”, so a retry never makes a second copy.
  • Redirects are refused, replies over 1 MiB are refused, and ServiceDesk Plus’s own error text is never shown.

Removing the connector deletes its sealed credentials in Plugboard, but does not revoke the token at Zoho. Delete the Self Client in the Zoho API console too.

While the school runs both, keep one queue in charge of new work. With the built-in ticket queue on as well, a repair can open a ticket in both systems, and the connectors page warns about it. When you cut over to Plugboard, disable this connector.

See connector configuration for shared setup concepts and the capability reference for the full limits.