> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-visualization-tools/hex.md).

# Hex

An overview of the Hex integration with Secoda

{% content-ref url="/pages/pMrc5yfyf9P7vAtsdgNT" %}
[Hex Metadata Extracted](/integrations/data-visualization-tools/hex/hex-metadata-extracted.md)
{% endcontent-ref %}

## Getting started with Hex

There are two steps to connect Hex with Secoda

1. Create a Personal or Workspace access token within Hex
2. Connect Hex to Secoda

### **Create a Personal Access or Workspace Token**

1. Navigate to `Settings` > `API Keys`
2. Create either a Personal access or Workspace token.

   **Note:** If using a Personal access token, the token will mirror the user's permissions in the workspace and will expire by the chosen date. Only workspace admins can create a Workspace token and this token has the option to never expire. For more information on tokens see (<https://learn.hex.tech/docs/explore-data/notebook-view/hex-api/hex-api-overview#token-creation>)

### **Connect Hex to Secoda**

After creating an access token, the next step is to connect Hex to Secoda

1. In the Secoda App, navigate to the 'Integrations' tab
2. Click on 'Connect Integration'
3. Search for and select 'Hex'
4. Add your Hex workspace\_id from your Hex workspace url. Ex:\
   For url "<https://app.hex.tech/bef6291f-4d04-40c2-bc5e-53ee21a29aea/home>" the workspace\_id will be "bef6291f-4d04-40c2-bc5e-53ee21a29aea"
5. Add the access token
6. Test the Connection - if successful, you'll be prompted to run your initial sync


---

# 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.secoda.co/integrations/data-visualization-tools/hex.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.