> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/6.0/6.1/app-registration/zendesk-tickets.md).

# Zendesk Tickets

### **Setup the App and Administrator account**

Sign up with Zendesk: <https://www.zendesk.com/register/>

### **2. Register OAuth app**

Now you need to add an OAuth application in Admin Center. In Admin Center navigate to: Apps and integrations > Connections > OAuth Clients.

Click Add OAuth client.

<figure><img src="https://content.gitbook.com/content/cfhstxIZQWZNvWjV2O6F/blobs/HCbFBzCa3HdvX5Pb1a3t/zendesk-tickets-2.png" alt=""><figcaption><p>OAuth Clients - empty</p></figcaption></figure>

#### Specify client details

<figure><img src="https://content.gitbook.com/content/cfhstxIZQWZNvWjV2O6F/blobs/rOlJdkpJIttkpTKHfcMK/zendesk-tickets-3.png" alt=""><figcaption><p>Specify name, description, company and logo</p></figcaption></figure>

#### Specify identifier and callback urls

<figure><img src="https://content.gitbook.com/content/cfhstxIZQWZNvWjV2O6F/blobs/lpntOKQjOo6UDUCh8T82/zendesk-tickets-4.png" alt=""><figcaption><p>Specify unique client ID and redirect URLs</p></figcaption></figure>

#### Generate client secret

Now save the OAuth client and copy the client ID and secret. You will need them later.

<figure><img src="https://content.gitbook.com/content/cfhstxIZQWZNvWjV2O6F/blobs/dB0k7lcoXa9WNelgmi46/zendesk-tickets-5.png" alt=""><figcaption><p>Make sure to copy the token</p></figcaption></figure>

Your OAuth client is now ready to be used and looks like this in the list of OAuth clients.

<figure><img src="https://content.gitbook.com/content/cfhstxIZQWZNvWjV2O6F/blobs/KEsnQzAxV2BM8kYu5qoT/zendesk-tickets-6.png" alt=""><figcaption><p>Make sure to copy the token</p></figcaption></figure>

#### Set `clientId`, `clientSecret` and `subdomain` into Appmixer Backoffice.

The last step is to configure clientId, clientSecret and subdomain in the Appmixer Backoffice for `appmixer:zendeskTickets` connector.

Note that the `subdomain` is the first part of your Zendesk URL. For example, if your Zendesk URL is `https://mycompany.zendesk.com`, then your subdomain is `mycompany`. In our example, the subdomain is `acme`.

<figure><img src="https://content.gitbook.com/content/cfhstxIZQWZNvWjV2O6F/blobs/Z06ji4VI8KrfNmYPke51/zendesk-tickets-7.png" alt=""><figcaption><p>Backoffice Zendesk Tickets connector configuration</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/6.0/6.1/app-registration/zendesk-tickets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.