How to build Webflow dashboards in Metabase

Webflow is a visual-first website platform whose CMS collections, forms, and e-commerce power design-led marketing sites. Metabase is where you turn that site data into shared, trustworthy dashboards. This guide covers two complementary paths: a lightweight MCP + CLI route that pulls live data with the Webflow MCP server and loads a CSV into Metabase with the Metabase CLI, and a durable pipeline route that syncs Webflow stats into a database so you can build dashboards anyone can read.

How do you connect Webflow to Metabase?

Most teams combine both routes: use MCP and CLI uploads for a fast first pass, then move recurring site reporting to a warehouse-backed model.

What can you analyze from Webflow data in Metabase?

• Content inventory by collection and status — built from CMS items and form submissions and the related collections, e-commerce orders, site publishes data your connection exposes.
• Form submissions by form and week — built from CMS items and form submissions and the related collections, e-commerce orders, site publishes data your connection exposes.
• Publishing cadence and site updates — built from CMS items and form submissions and the related collections, e-commerce orders, site publishes data your connection exposes.
• E-commerce orders and revenue — built from CMS items and form submissions and the related collections, e-commerce orders, site publishes data your connection exposes.
• Traffic per page from Analyze (where enabled) — built from CMS items and form submissions and the related collections, e-commerce orders, site publishes data your connection exposes.

Which Webflow dashboards should you build in Metabase?

How do you use the Webflow MCP server with the Metabase CLI?

Pair the Webflow MCP server with the Metabase CLI for fast, hands-on analysis. MCP is useful for scoped lookups and summarized exports; the Metabase CLI's upload command loads CSV data into Metabase and creates a ready-to-query table and model.

Example workflow

• Ask the MCP server for an inventory of CMS items and form submissions with created, published, and updated dates.
• Export the result as CSV, keeping stable IDs, statuses, and dates as columns.
• Run mb upload csv to load it into Metabase as a table and model, then build questions and dashboards on top.

Be honest about the limits

• MCP lookups are excellent for exploration, not scheduled reporting.
• A CSV upload is a snapshot; refresh it with mb upload replace or move to a durable route for real history.
• Item timestamps support inventory and cadence analysis from day one; traffic trends need the Analyze add-on or an external analytics tool.
• mb upload csv needs an uploads database configured under Admin → Settings → Uploads.

How do you set up Webflow MCP and the Metabase CLI?

{
  "mcpServers": {
    "webflow": {
      "url": "https://mcp.webflow.com/mcp"
    }
  }
}

Legacy clients can connect through npx mcp-remote https://mcp.webflow.com/sse, and a local webflow/mcp-server package exists. OAuth installs a small MCP Bridge App into the workspace you authorize.

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a CMS-items-and-form-submissions export — creates a table AND a model
mb upload csv --file webflow-CMS-items-and-form-submissions.csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file webflow-CMS-items-and-form-submissions.csv

Can you generate a Webflow dashboard with AI?

Yes. Use the prompt below with any assistant that can run the Webflow MCP server and the Metabase CLI. It works end to end: if Webflow tables already exist in Metabase it analyzes those; otherwise it pulls scoped, summarized data over MCP, loads it with mb upload csv, then builds the dashboard and caveats any metric that needs missing history.

Create a polished Metabase dashboard for Webflow content operations analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help site and content owners understand CMS inventory health, form conversions, e-commerce orders, and publishing cadence from Webflow data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for webflow tables and
  models). If durable Webflow data is already present — synced from a warehouse or uploaded earlier — use it and skip to Step 2.
- If nothing is there, pull a scoped, summarized export with the Webflow MCP server:
  CMS items and form submissions, plus collections, e-commerce orders, site publishes.
  Write each result to a CSV, then load it with the Metabase CLI — run
  "mb upload csv --file <export>.csv" so each upload creates a table and a
  ready-to-query model. Use "mb upload replace <table-id> --file <export>.csv"
  to refresh an existing table instead of creating duplicates.

Step 2 — Inspect before querying:
Do not assume exact table or column names. Inspect available content types,
statuses, dates, and whether daily history exists before creating trend cards.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  the Webflow API — it reads a database or CLI-uploaded tables.
- Exclude revisions, autosaves, and test entries from headline content counts.
- Only compute rates (conversion, open rate, paid share) when both numerator
  and denominator exist in the data.
- A single CSV is a point-in-time snapshot: only build trend cards if there is
  a usable date column or multiple periods have been uploaded.

Dashboard title: Webflow Content Operations Overview

Sections:
1. Executive summary: Items by status; Submissions this month; Orders;
   Items published this month.
2. Inventory: Items by collection and status; stale items not published in 6+ months.
3. Forms: Submissions by form and page by week.
4. Commerce: Orders, revenue, and AOV by week — only where Webflow Ecommerce is enabled.
5. Cadence: Items created vs. published by week.

Note: traffic data exists only for sites on the Analyze add-on; otherwise pull
sessions from GA4 or Plausible instead of inventing them.

Filters: Date range, Content type/Collection, Status, Author/Editor.

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. Include caveats for any metric
that cannot be calculated from the available data.

How do you sync Webflow data into a database or warehouse?

For dashboards that need history and reliability, land Webflow stats and entities in a database first, then connect Metabase to that database.

Connector options

• Managed ETL — use a connector when one covers the objects you need.
• Custom pipeline — use the Webflow Data & Analyze APIs for control over grain, fields, and refresh cadence.
• MCP + CSV — use this for quick exploration and one-off slices.

Skip the Airbyte Webflow source — it targets the v1 API, deprecated since March 2025, and new v1 tokens can no longer be created. Script the v2 Data API for CMS items, forms, and orders; sites on the Analyze add-on can also pull traffic time-series from the Analyze API (beta since June 2026).

Notes

• Land raw entity tables first, then build clean Metabase models on top.
• Normalize collection, item status, created, published, and updated dates fields.
• Keep platform stats (views, sessions) separate from measured analytics tools' numbers — definitions differ, and gaps are normal.

How should you model Webflow data in Metabase?

Core tables

Modeling advice

• Build a clean cms_item_inventory model with consistent columns, so dashboards survive schema changes and plugin swaps.
• Filter out revisions, autosaves, drafts-of-drafts, and internal test entries once, in the model — not in every question.
• Normalize URLs (lowercase, no protocol, no trailing slash) so CMS content joins cleanly to analytics and Search Console data.
• Store dates in UTC and convert at display time; CMS installs often run in site-local timezones.

Which Webflow metrics should you track in Metabase?

What SQL powers Webflow dashboards in Metabase?

These assume Webflow data synced into a warehouse (PostgreSQL dialect). Adjust table and column names to match your pipeline.

SELECT
  collection_id,
  COUNT(*) AS items,
  COUNT(*) FILTER (WHERE is_draft) AS drafts,
  COUNT(*) FILTER (WHERE is_archived) AS archived,
  COUNT(*) FILTER (
    WHERE NOT is_draft
      AND NOT is_archived
      AND last_published < CURRENT_DATE - INTERVAL '6 months'
  ) AS stale_items
FROM webflow_cms_items
GROUP BY 1
ORDER BY items DESC;

SELECT
  date_trunc('week', submitted_at) AS week,
  form_name,
  COUNT(*) AS submissions
FROM webflow_form_submissions
GROUP BY 1, 2
ORDER BY 1, 3 DESC;

SELECT
  date_trunc('week', accepted_on) AS week,
  currency,
  COUNT(*) AS orders,
  ROUND(SUM(total), 2) AS revenue,
  ROUND(SUM(total) / NULLIF(COUNT(*), 0), 2) AS avg_order_value
FROM webflow_orders
WHERE payment_status = 'PAID'
GROUP BY 1, 2
ORDER BY 1, 2;

What are common mistakes when analyzing Webflow in Metabase?

Related

Related analytics

Related dashboards

Related integrations

FAQ