Documentation sections

Measure

Connect dashboard data

A Data connection stores a MotherDuck token that SolidActions uses for Dashboard queries. The current public surface is MotherDuck-specific and is separate from workflow provider Connections.

Last reviewed July 14, 2026

In the app Measure → Data connections

Problems this solves

Start with the recurring problem, then use this feature when its boundary matches the outcome you need.

Problem

Connect live warehouse data to reporting

The data needed for a Dashboard already lives in MotherDuck, but the reporting surface has no safe way to query it.

How this helps

Add a protected Data connection so published and draft Dashboards can run their pinned queries against the permitted databases.

Problem

Separate reporting access from workflow credentials

A read-oriented dashboard should not inherit the broader OAuth accounts or secrets used by automation workflows.

How this helps

Use a dedicated MotherDuck read-scaling token and rotate it independently from workflow Connections and MCP sessions.

Add a MotherDuck connection

  1. Create a MotherDuck token for the identity and databases the dashboards need.
  2. Prefer a read-scaling token so the credential is limited to read-oriented workloads.
  3. Open Data connections and choose Add connection.
  4. Give it a name that identifies the source and environment, then paste the token into the password field.
  5. Create the connection and confirm its row reports an active state.

Use the least privilege available.

SolidActions checks Dashboard SQL as read-only, but the underlying token still determines what the query service can reach. Restrict the token to the databases and read permissions the dashboards actually require.

Use it from a Dashboard

Ask a connected AI to inspect the schema, create read-only queries, and bind the Dashboard to the named Data connection. The app executes only queries pinned into the selected published or draft revision. Query parameters come from filters declared by that dashboard.

Connection validation

SolidActions probes the token while creating the connection. A successful probe creates an Active row; a failed probe rejects the connection instead of leaving a Pending or Error row. If a previously accepted token later stops working, Dashboard queries fail until you replace the connection—the row is not a continuous health check.

Rotate a token

The current UI adds and removes Data connections; it does not expose the saved token for editing. Create a new connection with the replacement token, ask the AI to move affected Dashboard queries to it, verify their draft previews, publish, and only then remove the old connection.

Remove a connection

Removing a Data connection makes Dashboards that reference it stop working. Inventory those Dashboards and move them first. Removing the SolidActions record does not revoke the token in MotherDuck; revoke the old credential there as a separate cleanup step.

Know which Connection you need

  • Measure → Data connections: MotherDuck access for live Dashboard queries.
  • Automate → Connections: third-party OAuth credentials used by deployed workflows.
  • Settings → MCP Connections: authorized AI-client sessions for workspace tools.

Next: ask your AI to create a draft Dashboard.