rocketkind
Support

Zendesk

Zendesk is the support desk: tickets, the people who raise them, the organizations they belong to, and the agent groups that work them.

Authentication

  • OAuth 2.0

Actions

Generic API request. Call any Zendesk API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Add ticket tagsAdd tags to an existing Zendesk ticket without touching any of its other fields.
  • Create many ticketsBulk-create up to 100 Zendesk tickets (POST /tickets/createmany.json, JSON body { tickets: [...] }).
  • Create organizationCreate a Zendesk organization — the account-level grouping users belong to — so tickets can be attributed to a company.
  • Create ticketOpen a new Zendesk support ticket with a subject and an opening comment, optionally setting priority, status and type up front.
  • Create userCreate a Zendesk user — an end user or an agent, depending on role — so tickets can be raised by or assigned to them.
  • Delete ticketDestructiveDelete a Zendesk ticket by id (DELETE /tickets/{id}.json).
  • Delete userDestructiveDelete (deactivate) a Zendesk user by id (DELETE /users/{id}.json).
  • Get organizationRetrieve a single Zendesk organization by id (GET /organizations/{id}.json).
  • Get ticketRead one Zendesk ticket by id to see its current subject and status — the check to run before updating or commenting on it.
  • Get userRead one Zendesk user by id to confirm who a ticket's requester or assignee actually is before acting on their behalf.
  • List groupsBrowse the agent groups on the Zendesk account, typically to find the group id a ticket should be routed to.
  • List organizationsBrowse the organizations on the Zendesk account, to map a company name back to an organization id before creating or filtering tickets.
  • List ticket commentsRead the conversation on one Zendesk ticket in order — the way to get the full context of an issue, including which replies were public and which were internal notes.
  • List ticketsBrowse the tickets on the Zendesk account to see the current queue and to find a ticket id for zendesk:getticket or :updateticket.
  • List usersBrowse the users on the Zendesk account, end users and agents alike, to map a name or email address back to a user id.
  • SearchRun a Zendesk unified search (GET /search.json?query=...).
  • Update ticketDestructiveChange an existing Zendesk ticket: retitle it, move its status or priority, or append a public, customer-visible comment to the conversation.
  • Update userDestructiveChange an existing Zendesk user's display name, primary email address or role.

Triggers

  • Customer comments on ticketsAnswers as an agent in Zendesk: when a customer adds a public comment to a ticket, the agent replies on that ticket with a public comment.
  • New or updated organizationStarts when an organization is created or changes in the connected Zendesk account.
  • New or updated ticketStarts when a Zendesk ticket is created or updated.
  • New or updated userStarts when a user is created or changes in the connected Zendesk account.
  • Ticket comment addedStarts when a public reply or internal note is added to a Zendesk ticket.
  • Ticket createdStarts when a new Zendesk ticket is created, delivered in real time via Zendesk's native event-subscription webhook.
  • Ticket status changedStarts when a Zendesk ticket's status changes, for example from open to pending or solved.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.