Firecrawl Dashboard Reporting

by firecrawl94cc91229d6cISC185 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 6 weeks ago

Pull metrics from analytics dashboards and internal web tools with Firecrawl browser. Use when the user needs dashboard reporting, cross-platform metric summaries, authenticated analytics extraction, date-range reports, or structured metrics from web dashboards.

Instructions onlyData & Analytics
AI-generated overview

Extracts visible metrics from authenticated analytics dashboards via Firecrawl browser and compiles a structured report.

What it does
Guides an agent through collecting metrics from dashboards the user can legitimately access, using the Firecrawl browser to open dashboards, set date ranges, and read KPI cards, tables, and labels. It can click tabs, expand sections, scroll tables, and use export buttons when allowed. It produces a markdown dashboard report with a summary, metrics by dashboard, captured tables or exports, notes and caveats, and rerun inputs, plus a defined JSON shape.
When to use it
Use when the user needs dashboard reporting, cross-platform metric summaries, authenticated analytics extraction, date-range reports, or structured metrics pulled from web dashboards. It fits situations where numbers live in browser-based analytics or internal tools rather than in a queryable dataset.
Requirements
A Firecrawl API key (FIRECRAWL_API_KEY) for hosted Firecrawl requests, network access, and legitimate access to the target dashboards. It ships no scripts; it is instructions only.

Firecrawl Dashboard Reporting

Use this to extract visible metrics from dashboards the user can legitimately access.

Onboarding Interview

Infer dashboard URLs, metrics, date range, and output format from context. If dashboard targets are clear and accessible, proceed immediately.

Ask at most 1-3 concise questions only if blocked, such as the dashboard URLs, auth/profile requirement, or date range.

Firecrawl Collection Plan

Use Firecrawl browser for authenticated dashboards and UI interaction:

  • open each dashboard
  • set or verify date range
  • extract visible KPI cards, tables, and labels
  • click tabs, expand sections, and scroll tables
  • use export/download buttons only when appropriate and allowed

If login has expired, ask the user to re-authenticate rather than attempting to bypass access controls.

Parallel Work

If appropriate, use sub-agents or equivalent parallel task runners. Split by dashboard platform or metric category. Each researcher should return metrics, units, period, source URL, and caveats.

Final Deliverable

markdown
# Dashboard Report
## Summary[Highlights, alerts, trends]
## Metrics By Dashboard[Platform, metric, value, unit, change, period]
## Tables Or Exports[Captured tables/files and what they contain]
## Notes And Caveats[Auth issues, chart-only data, unavailable metrics]
## Rerun Inputsworkflow: firecrawl-dashboard-reportingdashboards: [urls]date_range: [range]metrics: [list]output: [json/markdown]

JSON Shape

Use reportedAt, dateRange, dashboards[], metrics[], tables[], exports[], and summary.

Quality Bar

  • Extract actual numbers, not just chart labels.
  • Note when a chart cannot be read precisely.
  • Preserve date ranges and source URLs.

Source and attribution

Source:firecrawl/firecrawl-workflowsinskills/firecrawl-dashboard-reportingat commit94cc912

License: ISC

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal