Tools used in this workflow
This workflow uses a write operation. Your AI agent will confirm the tile list before saving the dashboard.
| Tool | Required? | Notes |
|---|---|---|
| Scrunch MCP | Required | Uses create_explorer_dashboard, which writes a saved dashboard to your Scrunch organization |
Tips
Building this for a client vs. for internal use
Building this for a client vs. for internal use
For a client-facing dashboard, keep the tile count to 5-6 and favor card tiles for headline numbers — clients want a fast read, not a data exploration surface. For an internal team dashboard, add more granular breakdowns (per-platform, per-tag) since the audience is more likely to dig in.
Updating an existing dashboard vs. creating a new one
Updating an existing dashboard vs. creating a new one
create_explorer_dashboard always creates a new saved dashboard rather than editing one in place. If you’re refreshing a recurring dashboard, either keep using the same link (dashboards reflect live data automatically, so tiles update without a rebuild) or explicitly ask for a new dashboard only when the tile mix itself needs to change.Pairing this with generate_explorer_chart
Pairing this with generate_explorer_chart
If you just want to sanity-check one chart before committing to a full dashboard, ask Claude to generate a single Explorer chart first. Once you like how a metric looks, fold it into the dashboard tile list in Step 1.
Using the link in other workflows
Using the link in other workflows
Drop the dashboard link into a QBR deck appendix, a stakeholder email, or a Slack pin — it’s a live view, so anyone with the link always sees current data without needing you to re-run anything.
Auto-Build a QBR Deck
Use this dashboard link as a live companion to a static QBR deck.
Monthly Client Report, Built Automatically
For a written narrative report instead of a live clickable dashboard.