# Hex Integration Discovered Resources ## Overview The Hex Technologies integration discovers the following resources: * Hex Workspace * Hex Project ## Hex Workspace A single resource of type "hex\_workspace" is observed for each configured Hex integration. ### Properties | Property | Value | | -------- | ----------------------------- | | name | The name of the Hex workspace | | type | always `hex_workspace` | | subtype | always `hex_workspace` | ## Hex Project Projects are the main analytical resources in Hex, containing notebooks, data applications, and other analytical content. ### Properties | Property | Value | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | name | The title of the Hex project | | type | always `hex_project` | | subtype | always `hex_project` | | description | The description of the project, if provided | | native\_id | The unique project ID in Hex | | created\_at | The timestamp when the project was created | | updated\_at | The timestamp when the project was last edited | | created\_by | The email address of the user who created the project | | is\_active | Boolean indicating if the project is active (not trashed) | | total\_impressions\_30d | Total number of app views in the last 30 days This property is only available for published Hex Projects. | | total\_impressions\_14d | Total app views over the past 14 days. This property is only available for published Hex Projects. | | last\_viewed\_at | The timestamp when the project was last viewed | | tags | All the Hex Categories associated with the project. See [Hex Documentation](https://learn.hex.tech/docs/organize-content/statuses-categories#categories) | | meta.status | The project status if available. See [Hex Documentation](https://learn.hex.tech/docs/organize-content/statuses-categories#statuses) | | owner | The owner of the Hex project | | is\_published | Indicates whether the Hex Project has been published as an app. | | native\_last\_data\_update | Date of the most recent data refresh. | | last\_published | Date of the most recent edit to the published project. | ### Usage Analytics The Hex integration captures detailed usage analytics for projects: * **App Views**: Track how often projects are viewed as applications * **Time-based Metrics**: Separate tracking for 14-day and 30-day periods * **Last Activity**: When the project was most recently accessed ### Project Organization Projects are organized with the following structure: * **Workspace Level**: All projects belong to a parent workspace * **Categorization**: Projects can be tagged with categories for organization * **Status Tracking**: Projects have status information (if available) * **Ownership**: Clear attribution to creating and owning users ## Lineage Hex queries are distinguishable in the data warehouse's query history. See [Hex Documentation](https://learn.hex.tech/docs/explore-data/cells/sql-cells/sql-cells-introduction#query-metadata) for how Hex tags each query with metadata about the originating project and user. Euno leverages Hex's query metadta feature to build the lineage and usage information about Hex projects. See the relevant parts in each warehouse integration documentation. ## Relationships * **Hex Workspace → Hex Projects**: Projects are considered children of their parent workspace ### Container Relationships * Projects maintain a container chain showing their hierarchical position within the workspace structure * The workspace serves as the top-level container for all projects These relationships allow you to understand the organization of your Hex analytics environment and how different projects relate to each other within workspaces. ## Known Limitations Due to current Hex API constraints, the completeness of extracted metadata is affected. In particular, lineage in Euno is derived from query history, meaning only queries executed within the last 7 days are considered when building lineage for Hex projects. As a result: * **Delayed updates**: If a project is modified in a way that changes its lineage, it may take time for Euno to reflect these changes. During this period, the old and new lineage may appear overlapped. * **Missing lineage for inactive projects**: If a project has not been executed in the past 7 days, and no queries are available, Euno will be unable to detect or display its lineage. --- # Agent Instructions: 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: ``` GET https://docs.euno.ai/sources/analytics-notebooks/hex-technologies/hex-integration-discovered-resources.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.