> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/zendesk/getting_started/requirements.md).

# Requirements

Make sure the following requirements are fulfilled before you get started.

Prior to setting up Zendesk, please make sure to have the following: 

* One or multiple active Zendesk instances.
* Any of the following Zendesk Licenses: Team, Growth, Professional, Enterprise, or Enterprise Plus.
* A Zendesk service account with full admin permissions for Zendesk.
  * Verify the service account has the ability to install Zendesk support apps.
* A Nightfall admin account to complete the setup process. 

### Process

The user, with the Zendesk service account, will log into the Nightfall app to establish the OAuth connection between Nightfall and Zendesk.

1. Start by logging in to the Nightfall console at [app.nightfall.ai](http://app.nightfall.ai/). 
2. Once logged in, please navigate to the Zendesk option, on the left-hand side of the console.
3. Follow the 'Installing Nightfall for Zendesk' guide to complete the setup.


---

# 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://help.nightfall.ai/zendesk/getting_started/requirements.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.