Gitpulse
Merged
Size
M
Change Breakdown
Feature90%
Testing5%
Maintenance5%
#28099feat(API): Add insights summary endpoint to public API

Insights summary metrics now accessible via public API

Insights summary metrics now accessible via public API
AL
alielkhateeb
·Apr 7, 2026

API consumers can now pull workflow execution insights—successes, failures, runtime, and time saved—directly from n8n's public API with optional date and project filtering.

n8n users who track workflow performance now have a direct path into their metrics data. A new public API endpoint exposes workflow execution summaries including success and failure counts, failure rates, average runtimes, and time saved calculations.

The endpoint accepts optional filters: specify a date range using ISO 8601 timestamps, or narrow results to a specific project. When no dates are provided, it defaults to the last seven days. Requests require the insights:read scope and respect license limits on how far back data can be queried.

This unlocks programmatic access for building custom dashboards, generating reports, or feeding workflow analytics into external business intelligence tools. Teams no longer need to extract this data manually or rely solely on the n8n UI.

View Original GitHub Description

Summary

https://www.loom.com/share/fbac4a85fadd4bfda033b32a1941da21

Adds a GET /insights/summary endpoint to the n8n public API, allowing API consumers to retrieve workflow execution summary metrics (successes, failures, runtime, time saved) with optional date range and project filtering.

Changes:

  • New GET /v1/insights/summary endpoint with insights:read scope requirement
  • Query params: startDate, endDate, projectId (all optional; defaults to last 7 days)
  • License validation — respects feat:insights:viewSummary and quota:insights:maxHistoryDays
  • OpenAPI spec updated with paths and schema definitions
  • Integration tests covering success cases, validation errors, scoping, and license gating

Related Linear tickets, Github issues, and Community forum posts

https://linear.app/n8n/issue/LIGO-243

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)
© 2026 · via Gitpulse