> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/helpdesk-integrations/zendesk/forward-recordings-to-zendesk.md).
# Forward recordings to Zendesk
Auto-create Zendesk tickets when recordings are submitted through Screendesk links outside Zendesk.
The **Forward Recordings to Zendesk** feature lets you automatically create Zendesk tickets whenever a recording is submitted through Screendesk.
This is useful if you’ve added Screendesk links or buttons to sources outside Zendesk, such as:
* A button in your product.
* A Screendesk link in emails.
Whenever a recording is submitted, a Zendesk ticket is created with the recording attached, ensuring all customer issues are centralized in one place.
This feature simplifies support management and ensures no customer request is missed.
## Forward recordings to Zendesk
Visit the [integrations tab](https://app.screendesk.io/integrations) to enable this feature. Simply update the email field and hit save.
You can refer to this [article](https://support.zendesk.com/hc/en-us/articles/4408842868506-Adding-support-email-addresses-for-users-to-submit-tickets) to find your Zendesk support address.
{% hint style="danger" %}
If you need users to be registered to send emails to your Zendesk support address then you should add **** as a user.
{% endhint %}
---
# 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.screendesk.io/helpdesk-integrations/zendesk/forward-recordings-to-zendesk.md?ask=&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.
