Omni
Euno's Omni integration supports auto-discovery of the following Omni resources:
Omni accounts (organizations)
Omni folders
Omni models (semantic layer containers for views and topics)
Omni views and topics
Omni dimensions and measures
Omni workbooks
Omni queries (tabs in workbooks)
Omni dashboards
Lineage to source tables and models
Users (when "Observe users" is enabled)
User groups (when "Observe groups" is enabled)
Usage data: To observe usage (impressions, views) on Omni workbooks and dashboards, you must also set up the Omni Usage integration. It is a separate push integration that receives usage data from your Omni instance.
What Euno discovers
The Omni source discovers organization structure, semantic layer resources, workbooks and dashboards, and (optionally) users and groups. Lineage includes Omni-to-Omni dependencies and, when configured, warehouse table lineage for Snowflake-backed models.
For property and relationship details, see Omni Integration Discovered Resources.
Setting up Omni integration
Overview
Omni is an analytics and business intelligence platform that enables users to explore, analyze, and visualize data directly in their cloud data warehouse. In Omni, data is organized into workbooks (with query tabs), dashboards, and models. Models contain views and topics that provide a semantic layer over your data warehouse tables.
To discover Omni resources, Euno connects to the Omni API using Organization API keys. The integration automatically discovers your Omni organization structure, including folders, models, workbooks, and their lineage to underlying data warehouse tables.
Step 1: Create Omni API Credentials
Generate Organization API Key
Log in to your Omni instance as an Organization Admin
Navigate to Settings → API Access → Organization keys
Click Generate new key
In the modal, enter a descriptive name for the API key (e.g., "Euno Integration")
Click Generate
Copy the key immediately. Note: API keys are only displayed once when created.
Important: The API key is only shown once. Store it securely—you won't be able to retrieve it again.
For more details, see Omni API authentication.
Step 2: Configure New Omni Source in Euno
Access the Sources Page
Go to the Sources page in Euno.
Click on Add New Source and select Omni from the list of supported platforms.
General Configuration
Asterisk (*) means a mandatory field.
Name*
Enter a name for your Omni source (e.g., "Omni - Analytics")
Instance*
Your Omni instance subdomain. For example, if your Omni URL is https://mycompany.omniapp.co, enter mycompany.
API Key*
The Organization API key from Step 1
Default Snowflake Account Identifier
The Snowflake account identifier (e.g., wh51692.eu-central-1) used to link Omni views to warehouse table resources for all Snowflake connections in this instance. You can also paste the full Snowflake host (e.g., wh51692.eu-central-1.snowflakecomputing.com); it is normalized to the account identifier. If your organization or account name contains underscores, enter the account identifier directly — Snowflake hostnames replace underscores with hyphens, so the identifier cannot be recovered from the host. Covers the common single-warehouse case. Leave empty for non-Snowflake instances; use per-connection overrides (see Advanced) when a connection uses a different warehouse. Requires a separate Snowflake source that observes those tables.
Step 3: Schedule
Enable the Schedule option.
Choose:
Weekly: Set specific days and times.
Hourly: Define the interval in hours (e.g., every 8 hours).
Recommended: Schedule Omni integration to run daily or every 12 hours to keep workbook lineage and metadata up to date.
Step 4: Resource Cleanup
To keep your data relevant and free of outdated resources, Euno provides automatic resource cleanup options. These settings determine when a resource should be removed if it is no longer detected by a source integration. For a detailed explanation on Euno's cleanup strategies, see: Resource Sponsorship in Euno.
Immediate Cleanup: Remove resources not detected in the most recent successful source integration run.
No Cleanup: Keep all resources indefinitely, even if they are no longer detected.
Step 5: Advanced Settings (Optional)
Click on the 'Advanced' section to display these additional configurations.
Observe users
When enabled, Euno observes users from Omni via the SCIM API (/api/scim/v2/users). Default: enabled. Requires an Organization API key.
Observe groups
When enabled, Euno observes user groups and memberships via the SCIM API (/api/scim/v2/groups). Default: disabled. Requires an Organization API key.
Ingest topic ai_context as glossary terms
When enabled, each Omni topic with non-empty ai_context creates a linked glossary term in the Universal domain. Euno refreshes its description and related resources on each crawl. Default: disabled.
Path filter
Allow/deny regex patterns for Omni folder paths. Affects which folders and workbooks are discovered. Default deny: omni-examples.*.
Model filter
Allow/deny regex patterns for Omni shared model names. Default deny: Ecommerce Demo Data.
Connection overrides
Optional per-connection overrides of the Default Snowflake Account Identifier, for Omni connections that use a different Snowflake warehouse than the default. Enter the Omni connection id (listed under Snowflake connections discovered in each run report) and its Snowflake account identifier. Connections without an override fall back to the default target. Requires a separate warehouse source (for example Snowflake) that observes those tables.
For additional information regarding Users & Groups see Users as a Resource.
Linked glossary terms from topic AI context
Linked terms are marked Managed by Omni in the Data Glossary. Their descriptions come from the topic's ai_context and cannot be edited in Euno. You can still edit the term name, owner, domain, synonyms, tags, external links, and your related resources. Euno keeps the Omni-managed related-resource set separate, so a crawl refresh does not replace manual selections or a defining EQL.
Euno links the topic, its dimensions and measures, and downstream Omni queries and dashboards. If a topic's ai_context becomes empty, the topic disappears, or you turn the setting off, Euno removes the linked term on the next crawl. If the topic name conflicts with a manually created term in the Universal domain, Euno keeps the manual term unchanged and reports the conflict in the crawl processing results.
Step 6: Save Configuration
Click the Test & Save button to complete the setup. Euno will:
Validate the instance URL is accessible
Authenticate using the provided API key
Verify access to the Omni organization
Save the configuration if all validations pass
If the test fails, review the error message and verify your API key and instance subdomain are correct.
Last updated