> For the complete documentation index, see [llms.txt](https://doc.product-reg.varify.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.product-reg.varify.xyz/integrations/gorgias.md).

# Gorgias

### Setup

Gorgias supports HTTP integrations, allowing it to call external API endpoints to retrieve and display information directly within the Gorgias interface.

To set up the integration, follow the instructions provided in the [Gorgias HTTP Integration documentation](https://docs.gorgias.com/en-US/http-integrations-81822).

During the setup process, you will be prompted to provide an API endpoint. This endpoint will be used to fetch customer-related information, such as email or other details, from the app.

### Obtain the API Endpoint

The API endpoint for integrating with Gorgias is:

<https://product-reg.varify.xyz/api/gorgias/users?email={{ticket.customer.email}}>

This endpoint requires an authorization token (API key) to be included in the request headers, as specified in the Gorgias HTTP Integration guide. You can obtain the API key by navigating to **App Admin > App Settings > General > API Access Token** in the app.

Ensure the token is securely stored and used only for authorized requests.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.product-reg.varify.xyz/integrations/gorgias.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.