Requirements
For metadata ingestion, make sure to add at leastdata scopes to the clientId provided.
For questions related to scopes, see the domain scope documentation.
Metadata Ingestion
To ingest metadata from Domo Dashboard, you need to create a service connection. The service connects Domo Dashboard with Collate. Once you create a service, Collate automatically starts ingesting metadata.Step 1: Add New Service
- In the left navigation, click Connections.
- On the Connections page, click Add New Service.

Step 2: Select a Service and Connector
From the service type dropdown, select Dashboard Services, then click the Domo Dashboard connector tile.
Step 3: Add Service Name and Description
- Enter a unique, descriptive Service Name. Collate identifies services by their service name. Enter a name that distinguishes this deployment from other Domo Dashboard services you are ingesting metadata from.
- Optional: Enter a Description for the service.

Note: The service name cannot be changed after it is set.
Step 4: Configure Connection Options
Specify where ingestion runs, provide your source credentials, and verify the connection.Select Ingestion Runner
Select an Ingestion Runner: the runner where the ingestion pipeline will execute.
Enter Connection Details
Enter the connection details for Domo Dashboard. The right-hand panel in the UI displays inline help for each field.
- Client ID: Client ID to Connect to Domo Dashboard.
- Secret Token: Secret Token to Connect Domo Dashboard.
- Access Token: Access to Connect to Domo Dashboard.
- API Host: API Host to Connect to Domo Dashboard instance.
- Instance Domain: URL to connect to your Domo instance UI. For example
https://<your>.domo.com.
Test Connection
Once the credentials have been added, click on Test Connection and Save the changes.
Step 5: Configure Ingestion Options
In the What to Ingest step, use filter patterns to control which assets Collate ingests from your dashboard service. Filter patterns use regular expressions applied to asset names.How Filter Patterns Work
- Include: Add one or more comma-separated regular expressions. Collate ingests only assets whose names match at least one expression. Leave blank to include all assets.
- Exclude: Add one or more comma-separated regular expressions. Collate skips any asset whose name matches an expression. Leave blank to exclude nothing.
- contains: matches any name containing the value. For example,
salesmatchesmy_sales_dataandsales_2024. - starts with: matches names beginning with the value. For example,
prod_matchesprod_dbandprod_schema. - ends with: matches names ending with the value. For example,
_rawmatchesevents_rawandlogs_raw. - is exactly: matches the exact name only. For example,
analyticsmatches onlyanalytics. - matches regex: matches names using a regular expression. For example,
^prod_.*_v\d+$matchesprod_events_v1.
- Dashboard: Controls which dashboards Collate ingests from the source.
- Chart: Controls which charts within the ingested dashboards are included.
- Data Model: Controls which data models are included in metadata ingestion.
- Scan Mode: You can choose between the following scan modes:
- Scan all: Ingests every asset of that type the connector can access. This is the default.
- Only specific: Enables include rules so only assets matching at least one rule are ingested.
- Exclude system toggle: Use this toggle to automatically filter out system-reserved names defined by the connector — for example, Exclude system databases for the Databases section.
- Always exclude: Add permanent exclusion rules (shown in red). Assets matching these rules are never ingested, regardless of include rules.
- Preview: Shows a real-time summary of what will be in scope based on your current rules.
- Include rules (available only in Only specific mode): Click + Add to define a rule. Added rules appear as chips; an asset is included if it matches any rule.
Step 6: Create & Deploy
Click Create & Deploy to deploy the agent and start the first metadata ingestion run. Collate saves the service configuration and immediately begins pulling metadata from the source. To monitor ingestion progress or view the service you just added, go to Connections in the left navigation and select your service.Configure Metadata Agent and Schedule Ingestion
The Metadata Agent extracts dashboards, charts, data models, and other structural metadata from your source and keeps your Collate catalog in sync. It powers discovery, lineage, and governance across your data assets. When you click Create & Deploy, Collate automatically deploys a Metadata Agent for this service and triggers the first ingestion run. View its status and run history from the Agents tab on the service detail page. To configure the additional Metadata Agent and schedule ingestion, follow these steps:- In the left navigation, click Connections and select your service.
- Click the Agents tab.
-
Click Add Agent and select Metadata from the dropdown.
For some services, the dropdown is not available and clicking Add Agent takes you directly to the agent configuration page.
-
On the Configure Ingestion page, do the following and click Next.
-
Name this Ingestion: Enter a unique recognizable name for this ingestion pipeline.

-
Agent Setup: Configure ingestion parameters. The following fields are available:

-
Filter Patterns: Apply include or exclude rules to scope which dashboards, charts, data models, and projects this agent ingests. These follow the same filter options described in Step 5.

-
Scope & Behaviour: Control what metadata to include and how to handle deletions. Toggle each option on or off based on your needs:

-
Name this Ingestion: Enter a unique recognizable name for this ingestion pipeline.
-
On the Schedule Interval page, set when the agent runs:
- Schedule: Choose a preset interval (Hourly, Daily, Weekly, Monthly) or enter a custom cron expression.
- On-Demand: No automatic schedule; trigger the agent manually when needed.

- Click Add to deploy the agent.
Troubleshooting
Domo Dashboard Troubleshooting
Learn more about how to troubleshoot common Domo Dashboard connector issues and resolve configuration or ingestion errors.