Prerequisites
The Hex integration relies on query history to discover which tables Hex projects query. It is supported on BigQuery and Snowflake. Elementary’s service account must have permissions to read query history. Refer to your warehouse’s setup page for the required roles:If Elementary cannot read query history, the Hex integration will not discover any exposures.
Create API Token
Elementary needs a workspace token in your account in order to access Hex’s API on your behalf.To create one, please follow the official Hex documentation. Make sure you create a Hex Workspace token with read access for all categories and “read project queried tables”.
Connecting Hex to Elementary
Navigate to the Account settings > Environments and choose the environment to which you would like to connect Hex. Choose the Hex connection and provide the following details to validate and complete the integration.- Base URL: Your Hex workspace URL. For example:
https://app.hex.tech/my-workspace/ - Workspace Token: The Hex workspace token you’ve created on the previous step.
Hex queries on a different warehouse environment
By default, Elementary reads query history from the warehouse environments (e.g., BigQuery projects, Snowflake accounts) referenced in your dbt project. If Hex executes queries through a different environment (e.g., a dedicated Hex execution environment), you will need to:- Grant query history permissions — the same permissions required for your primary environment. See the prerequisites above for links to your warehouse’s permissions page.
- Let us know — contact Elementary support with the environment details so we can configure Elementary to also read query history from it.
Limitations
- Hex assets will only be visible if their project has run within the last 14 days. Elementary tracks Hex query history to determine asset visibility, and only projects with recent execution activity will appear in the lineage graph.

