Skip to content
plugboard.appRequest a demo

Connectors

Zendesk

For a school moving its desk from Zendesk to Plugboard. While the connector is on, a repair lodged in Plugboard raises its ticket in Zendesk as well, and the Plugboard ticket keeps the link to it; Plugboard can read a linked ticket’s status, add notes to it and close it; and the desk’s search can find the tickets still in Zendesk. Once the open work is across, turn the connector off.

CategoryTicketing
AuthenticationAPI token
Reacheshttps://yourorg.zendesk.com
Needs an agentNo
Demo modeNo

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

It is checked against recorded Zendesk responses, not against a school’s own Zendesk account. Run Save and test and one test repair against yours before the switch depends on it.

  1. In Zendesk, go to Admin Center, Apps and integrations, Zendesk API.
  2. Enable Token access if it is not already on.
  3. Add API token, describe it as Plugboard, and copy the token. It is shown once.
  4. Note the email address of the agent whose account the token belongs to.

The token authenticates as that agent, so tickets created by Plugboard are attributed to them. Use a dedicated integration agent account rather than a person, so the attribution stays meaningful and does not stop working when they leave.

Settings, Connectors, then Zendesk under Add a service, and Continue to setup.

FieldValue
baseUrlYour Zendesk URL, for example https://yourorg.zendesk.com
emailThe agent email the token belongs to
federatedSearchOptional. Includes Zendesk results in the desk’s search, run as this agent
FieldValue
apiTokenThe API token from step 3

Save and test.

Give the switch a cutover date and keep the overlap short, because work that sits in two queues gets done in neither.

  • Before cutover, connect Zendesk. Repairs raised in Plugboard then appear in Zendesk too, so the old desk stays complete while people still look there. Turn on federated search in the connector’s settings if the desk should find tickets still in Zendesk; see your external helpdesk for what that trades.
  • Carry the open tickets across by hand: raise each in Plugboard and close it in Zendesk with a note naming the new ticket. It is usually a few dozen. Closed tickets stay in Zendesk; see historical tickets do not migrate.
  • On cutover day, new requests go to Plugboard and you turn the connector off, so repairs raise their tickets in Plugboard alone. Keep Zendesk readable for as long as people need its history.

While the connector is on, each Plugboard status can carry an external status it maps to, set on the workflow page, so a status change here is reflected in Zendesk. Zendesk’s statuses are new, open, pending, hold, solved and closed.

A reasonable mapping:

PlugboardZendesk
Receivednew
In progressopen
Awaiting partshold
With vendorpending
Readypending
Closedsolved

Solved rather than closed for the last one, because Zendesk closes solved tickets itself after its own interval, and closing outright prevents a follow-up comment.

SymptomCause
401 on testToken access is disabled, the token is wrong, or the email does not match the token’s owner
403The agent lacks permission for that operation, usually on a restricted brand or group
404 on ticket operationsThe ticket was deleted in Zendesk, or the base URL points at the wrong subdomain
Tickets created but not updatedThe status mapping is empty, so nothing is being pushed
Duplicate ticketsThe same request was raised in both desks. Raise new work in Plugboard only