> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opsmatic.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow Analytics

> Track execution success, duration and error patterns for individual workflows

## Overview

Workflow Analytics drills into the performance of individual automations across your n8n and Make.com connections. Where the [Analytics overview](/analytics/overview) shows the big picture, this view answers "which workflow is failing, how often, and why?"

## Execution Metrics

Every workflow run Opsmatic sees is recorded as an **execution** with one of five statuses:

| Status      | Meaning                               |
| ----------- | ------------------------------------- |
| `success`   | Completed without error               |
| `error`     | Failed                                |
| `running`   | In progress                           |
| `waiting`   | Paused / waiting on an external event |
| `cancelled` | Stopped before completion             |

From these, Opsmatic derives the core per-workflow metrics:

<CardGroup cols={2}>
  <Card title="Success Rate" icon="circle-check">
    Share of executions that completed successfully over the selected period.
  </Card>

  <Card title="Average Duration" icon="clock">
    Mean execution time — the first place to look for slowdowns.
  </Card>

  <Card title="Execution Volume" icon="chart-column">
    How many times a workflow ran, and when its peaks are.
  </Card>

  <Card title="Failure Reasons" icon="triangle-exclamation">
    Captured error details grouped so you can see the dominant failure mode.
  </Card>
</CardGroup>

## Grouping by Workflow

The dashboard and the API can roll executions up per workflow so you can rank your automations by volume, failure rate or duration. Via the API:

```bash theme={null}
curl -H "Authorization: Bearer ops_your_api_key" \
  "https://api.opsmatic.com/v1/executions?connection_id=conn_abc123&group_by=workflow"
```

To pull the raw failing runs for one workflow, with error details:

```bash theme={null}
curl -H "Authorization: Bearer ops_your_api_key" \
  "https://api.opsmatic.com/v1/executions?workflow_id=wf_support_triage&status=error&include_error_details=true"
```

See the [Analytics API](/api-reference/analytics#executions) for all filters.

## Pre-computed Trends

For historical charts, Opsmatic maintains rolled-up aggregations so long-range views stay fast even after raw executions are purged. The relevant `metric_type` values are:

* `daily_executions`, `weekly_executions`, `monthly_executions`
* `daily_success_rate`, `weekly_success_rate`, `monthly_success_rate`
* `daily_avg_duration`, `weekly_avg_duration`, `monthly_avg_duration`

```bash theme={null}
curl -H "Authorization: Bearer ops_your_api_key" \
  "https://api.opsmatic.com/v1/analytics?metric_type=weekly_success_rate&connection_id=conn_abc123"
```

## Using the Data

<AccordionGroup>
  <Accordion title="Find your most fragile workflow">
    Group by workflow, sort by failure rate, then open the failing executions with `include_error_details=true` to read the actual errors.
  </Accordion>

  <Accordion title="Catch a regression early">
    Watch `avg_duration` trends — a steady climb usually points at a growing dataset, a slow upstream API, or an added node.
  </Accordion>

  <Accordion title="Plan capacity">
    Use execution volume peaks to schedule heavy workflows off your busiest windows.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Performance Metrics" icon="gauge" href="/analytics/performance-metrics">
    How to read and interpret the KPIs
  </Card>

  <Card title="Availability Monitoring" icon="server" href="/analytics/availability-monitoring">
    Platform uptime and response time
  </Card>
</CardGroup>