How to build Teamwork.com dashboards in Metabase

Teamwork.com is a client-work platform for projects, tasks, milestones, time, budgets, workload, profitability, Desk tickets, and Spaces docs. Metabase is where you turn that operational activity into shared, trustworthy dashboards. This guide covers two complementary paths: a lightweight MCP + CLI routethat pulls live data with the Teamwork.com MCP Server and loads a CSV into Metabase with the Metabase CLI, and a durable pipeline route that syncs Teamwork.com into a database so you can build dashboards anyone can read.

How do you connect Teamwork.com to Metabase?

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

What can you analyze from Teamwork.com data in Metabase?

• Client project health — built from tasks and the related projects, milestones, time entries data your sync exposes.
• Task and milestone completion — built from tasks and the related projects, milestones, time entries data your sync exposes.
• Billable time and utilization — built from tasks and the related projects, milestones, time entries data your sync exposes.
• Budget and profitability risk — built from tasks and the related projects, milestones, time entries data your sync exposes.
• Workload and capacity — built from tasks and the related projects, milestones, time entries data your sync exposes.

Which Teamwork.com dashboards should you build in Metabase?

How do you use the Teamwork.com MCP Server with the Metabase CLI?

Pair the Teamwork.com MCP Server with the Metabase CLI for fast, hands-on analysis. MCP is useful for scoped lookups and 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 overdue or recently completed tasks.
• Export the result as CSV, keeping stable IDs, owners, containers, status or type, and timestamps.
• 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 the pipeline for real history.
• Status history is required for true cycle time and time-in-status metrics.
• mb upload csv needs an uploads database configured under Admin → Settings → Uploads.

How do you set up Teamwork.com MCP and the Metabase CLI?

{
  "mcpServers": {
    "teamwork": {
      "url": "https://mcp.ai.teamwork.com"
    }
  }
}

# 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 tasks export — creates a table AND a model
mb upload csv --file teamwork-tasks.csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file teamwork-tasks.csv

Can you generate a Teamwork.com dashboard with AI?

Yes. Use the prompt below with any assistant that can run the Teamwork.com MCP Server and the Metabase CLI. It works end to end: if Teamwork.com tables already exist in Metabase it analyzes those; otherwise it pulls scoped 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 Teamwork.com work management analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help team and program leaders understand completion, throughput, overdue work, workload balance, and project health from Teamwork.com data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for teamwork tables and
  models). If durable Teamwork.com 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 export with the Teamwork.com MCP Server: tasks,
  projects, milestones, time entries. 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 fields, dates, owners,
containers, status values, and whether change/activity history exists before creating
duration or trend cards.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  Teamwork.com — it reads a database or CLI-uploaded tables.
- Only compute durations when the required start/end or event timestamps exist.
- Exclude archived, deleted, canceled, or test objects from active-population cards.
- Avoid individual performance leaderboards; use owner views for balancing and cleanup.
- 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: Teamwork.com Work Management Overview

Sections:
1. Executive summary: Completed work last 30 days; Open work; Overdue rate;
   Median cycle time if available; Unassigned work.
2. Throughput: Created vs completed by week; Completed work by type/status/project.
3. Project health: At-risk projects; blocked work; stale work; upcoming deadlines.
4. Workload: Open and overdue work by owner/team; WIP by status.
5. Flow: Cycle time, lead time, and time in status if history is available.

Filters: Date range, Project/board/database, Status, Owner, Team, Work type.

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 Teamwork.com data into a database or warehouse?

For dashboards that need history and reliability, land Teamwork.com data 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 Teamwork.com APIs for control over fields, history, and refresh cadence.
• MCP + CSV — use this for quick exploration and one-off slices.

Sync projects, tasks, milestones, time entries, budgets, users, workload allocations, Desk tickets, and Spaces documentation through Teamwork.com APIs.

Notes

• Land raw tables first, then build clean Metabase models on top.
• Keep change events or daily snapshots if you need trends and duration metrics.
• Normalize owner, team, project, status, due-date, and completed-date fields.

How should you model Teamwork.com data in Metabase?

Core tables

Modeling advice

• Build a clean work_items model with common columns across tools.
• Separate current-state fields from change events, activity, or snapshot history.
• Exclude archived, deleted, test, and duplicate objects from active-population metrics.
• Use stable IDs for owner, project, and item joins; display names can change.

Which Teamwork.com metrics should you track in Metabase?

What SQL powers Teamwork.com dashboards in Metabase?

These assume a cleaned analytical model in a warehouse (PostgreSQL dialect). Adjust table and column names to match your connector.

SELECT
  date_trunc('week', completed_at) AS week,
  COUNT(*) AS completed_items
FROM work_items
WHERE completed_at IS NOT NULL
  AND archived_at IS NULL
GROUP BY 1
ORDER BY 1;

SELECT
  project_name,
  COUNT(*) FILTER (
    WHERE completed_at IS NULL
      AND due_date < CURRENT_DATE
  ) AS overdue_items,
  COUNT(*) FILTER (
    WHERE completed_at IS NULL
      AND due_date IS NOT NULL
  ) AS open_items,
  ROUND(
    100.0 * COUNT(*) FILTER (
      WHERE completed_at IS NULL
        AND due_date < CURRENT_DATE
    ) / NULLIF(COUNT(*) FILTER (
      WHERE completed_at IS NULL
        AND due_date IS NOT NULL
    ), 0),
    2
  ) AS overdue_rate
FROM work_items
WHERE archived_at IS NULL
GROUP BY project_name
ORDER BY overdue_rate DESC NULLS LAST;

SELECT
  owner_name,
  COUNT(*) FILTER (WHERE completed_at IS NULL) AS open_items,
  COUNT(*) FILTER (
    WHERE completed_at IS NULL
      AND due_date < CURRENT_DATE
  ) AS overdue_items
FROM work_items
WHERE archived_at IS NULL
GROUP BY owner_name
ORDER BY open_items DESC;

What are common mistakes when analyzing Teamwork.com in Metabase?

Related

Related analytics

Related integrations

FAQ