Count screenshots

A collaborative canvas for data analysis, where SQL, charts and notes sit side by side.

Count

Connecting dbt to a BI canvas, with DuckDB to spare your database

Count lets you attach dbt Core or dbt Cloud metadata to a database connection with instructions beside the form, and offers DuckDB and caching toggles to reduce warehouse load.

B2BactivationMar 2025

01

dbt Core: two ways in

The dbt tab on a Supabase connection offers a GitHub app or a manifest upload, with a getting-started panel on the right.

Count: dbt Core: two ways in
  1. 1

    Value in one line (working)

    "Connect your dbt project to integrate model, source and test metadata with your tables" says what you gain.

    Reason-giving

  2. 2

    Core or Cloud in one dropdown (working)

    One Source picker switches the whole form between dbt Core and dbt Cloud.

    Progressive disclosure

  3. 3

    GitHub or upload (working)

    "Connect GitHub" is primary, "Upload artifact" is the fallback for teams that can't install apps.

    Flexibility and efficiency of use

  4. 4

    Instructions beside the form (working)

    Option a) and b) explain each button, with links to docs and "speak to one of the team".

    Contextual help

  5. 5

    Upsell where you add sources (working)

    "Upgrade this plan to add more connections" sits in the Connections list, where the limit is felt.

    Contextual timing

02

dbt Cloud: URL and token

Switching the source to dbt Cloud shows two fields and a three-step guide that spells out token permissions.

Count: dbt Cloud: URL and token
  1. 6

    Access URL prefilled (working)

    "cloud.getdbt.com" is filled in, so most users only need the token.

    Default effect

  2. 7

    One real input (working)

    The API token is the only field left to fill, which keeps the form short.

    Reduce friction

  3. 8

    Connect disabled until ready (working)

    The greyed-out button signals the form isn't complete yet.

    Error prevention

  4. 9

    Least-privilege token (working)

    "Read-only and Metadata only permissions" tells security-minded users exactly what to create.

    Trust signals

  5. 10

    Docs wall for later steps (not working)

    Steps 2 and 3 describe account and artifact choices that aren't on screen yet, so you read about manifest.json before you need it.

    Cognitive load

03

Connection settings: DuckDB and caching

Further down the connection page, Count offers ways to cut load on your database.

Count: Connection settings: DuckDB and caching
  1. 11

    Schema freshness shown (working)

    "Last updated on Mar 18, 2024" next to Refresh tells you how stale the table list is.

    Visibility of system status

  2. 12

    Benefit-led setting (working)

    "Enabling this setting can help to reduce database load" sells the DuckDB toggle in the description.

    Reason-giving

  3. 13

    Off by default (not working)

    The load-saving DuckDB option ships switched off, so most users never get the benefit.

    Default effect

  4. 14

    Half-disabled caching (not working)

    "Result caching is not enabled for this workspace" while "Cache results for 5 minutes" looks selected; it's unclear what is active.

    Clarity

  5. 15

    Danger zone set apart (working)

    "Delete connection" sits alone under its own heading in red outline.

    Error prevention

Takeaways from Count

  1. Put setup instructions next to the form, one block per path, and name the exact token permissions needed.
  2. Prefill whatever is the same for most users (like the dbt Cloud URL) so the form shrinks to the one thing only they know.
  3. If a setting protects the customer's database, consider making it the default instead of a toggle they have to discover.