Automations40k · #5147

flowstudio-power-automate-monitoring

Allows your agent to monitor Power Automate across the entire company. It shows failure rates, trends, and reports. Useful for getting an overview of flow usage and health.

What it does

This tool helps monitor the performance of automated flows in Power Automate. It shows failure rates, health trends, and an inventory of who created the flows, all aggregated for your entire organization.

When to use it

✓Check the overall health of all automated flows.
✓Identify frequently failing flows.
✓List all flows and their creators.

Example of what to ask your AI

“Show me the failure rate of all flows in the last 30 days.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/github/awesome-copilot/blob/main/skills/flowstudio-power-automate-monitoring/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/github/awesome-copilot/blob/main/skills/flowstudio-power-automate-monitoring/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.

View on GitHub ↗Raw file

How it works

The tool collects data about your automated flows daily and stores it in a secure location. This allows for quick queries without overloading the Power Automate system.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add github/awesome-copilot --skill flowstudio-power-automate-monitoring

Or download just the file:

curl -L https://raw.githubusercontent.com/github/awesome-copilot/main/skills/flowstudio-power-automate-monitoring/SKILL.md -o SKILL.md

Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Power Automate Monitoring with FlowStudio MCP

Monitor flow health, track failure rates, and inventory tenant assets through the FlowStudio MCP cached store — fast reads, no PA API rate limits, and enriched with governance metadata and remediation hints.

⚠️ Pro+ subscription required. This skill calls store_* tools that only work for FlowStudio for Teams or MCP Pro+ subscribers.

If the user does not have Pro+ access: the first store_* tool call will return a 403/404 error. When that happens:

STOP calling store tools

Tell the user this feature requires a Pro+ subscription

Link them to https://mcp.flowstudio.app/pricing

If their question can be answered with live tools (e.g. "list flows in one environment"), offer to use the flowstudio-power-automate-mcp skill instead

Discovery: load tool schemas via tool_search rather than tools/list — call with query: "select:list_store_flows,get_store_flow_summary" for the common monitoring tools, or load the full set with query: "skill:governance" (the server's governance bundle covers most monitoring reads too — this skill and flowstudio-power-automate-governance share the underlying tool family). This skill covers response shapes, behavioral notes, and workflow patterns — things tool_search cannot tell you. If this document disagrees with a real API response, the API wins.

How Monitoring Works

FlowStudio scans the Power Automate API daily for each subscriber and caches the results. There are two levels:

All flows get metadata scanned: definition, connections, owners, trigger type, and aggregate run statistics (runPeriodTotal, runPeriodFailRate, etc.). Environments, apps, connections, and makers are also scanned.
Monitored flows (monitor: true) additionally get per-run detail: individual run records with status, duration, failed action names, and remediation hints. This is what populates get_store_flow_runs and get_store_flow_summary.

Data freshness: Check the scanned field on get_store_flow to see when a flow was last scanned. If stale, the scanning pipeline may not be running.

Enabling monitoring: Set monitor: true via update_store_flow or the FlowStudio for Teams app (how to select flows).

Designating critical flows: Use update_store_flow with critical=true on business-critical flows. This enables the governance skill's notification rule management to auto-configure failure alerts on critical flows.

Tools

Tool	Purpose
`list_store_flows`	List flows with failure rates and monitoring filters
`get_store_flow`	Full cached record: run stats, owners, tier, connections, definition (`triggerUrl` field included)
`get_store_flow_summary`	Aggregated run stats: success/fail rate, avg/max duration
`get_store_flow_runs`	Per-run history with duration, status, failed actions, remediation (filter `status="Failed"` for errors-only view)
`update_store_flow`	Set monitor flag, notification rules, tags, governance metadata
`list_store_environments`	All Power Platform environments
`list_store_connections`	All connections
`list_store_makers`	All makers (citizen developers)
`get_store_maker`	Maker detail: flow/app counts, licenses, account status
`list_store_power_apps`	All Power Apps canvas apps

For start/stop, use set_live_flow_state from the monitor-flow bundle (tool_search query: "select:set_live_flow_state") — the cache resyncs on the next scan. The previous set_store_flow_state convenience wrapper is deprecated.

Store vs Live

Question	Use Store	Use Live
How many flows are failing?	`list_store_flows`	—
What's the fail rate over 30 days?	`get_store_flow_summary`	—
Show error history for a flow	`get_store_flow_runs` (filter `status="Failed"`)	—
Who built this flow?	`get_store_flow` → parse `owners`	—
Read the full flow definition	`get_store_flow` has it (JSON string)	`get_live_flow` (structured)
Inspect action inputs/outputs from a run	—	`get_live_flow_run_action_outputs`
Resubmit a failed run	—	`resubmit_live_flow_run`

Store tools answer "what happened?" and "how healthy is it?" Live tools answer "what exactly went wrong?" and "fix it now."

…

FAQ

Do I need to pay to use this tool?

Yes, this tool requires a FlowStudio Pro+ subscription to function, as it accesses historical and aggregated data.

Can I see details of a specific flow or fix an error?

No, this tool is for overview and aggregated views. For specific flow details or to fix errors, you would need to use other tools like flowstudio-power-automate-mcp or flowstudio-power-automate-debug.

How often is the data updated?

Data is collected daily. You can check the 'scanned' field in a flow record to see when it was last updated.

Details

Original description by the author

Pro+ subscription required. Tenant-wide Power Automate monitoring using the FlowStudio MCP cached store: failure rates, run-health trends, maker/app inventory, inactive owners, and compliance/health reports. Use only for aggregated tenant views. For one environment, one flow, run control, or root-cause debugging, use flowstudio-power-automate-mcp, flowstudio-power-automate-debug, or the server mon

repo: github/awesome-copilot

Popularity

GitHub stars: 40k
Ranking position: #5147
License: MIT
Updated: 10/15/2026

Is this skill useful?

Comments

More skills from this repository

Documentation40k

acquire-codebase-knowledge

Helps your agent understand and document an existing code project. It's useful for onboarding new people or getting an overview of the architecture.

github/awesome-copilot

Documentation40k

acreadiness-assess

Enables your agent to assess a project's readiness for AI and generate a report. It's useful for understanding how well a project is prepared to use AI tools.

github/awesome-copilot

Documentation40k

acreadiness-generate-instructions

Helps your agent create instructions for AI tools based on an assessment. It's useful for improving how AI interacts with code and closing identified gaps.

github/awesome-copilot

Agents40k

acreadiness-policy

Enables your agent to help define or apply policies for AI project assessment. It's useful for standardizing how projects are evaluated and ensuring compliance.

github/awesome-copilot

Similar skills

Automations280k

benchmark

Helps your agent measure code speed and performance. It's useful for ensuring things are fast and finding slowness issues.

affaan-m/ECC

Automations280k

content-hash-cache-pattern

Lets your agent use content hashes to cache file processing results. This avoids repeated processing and auto-invalidates the cache when content changes. Useful for speeding up slow tasks.

affaan-m/ECC

Automations280k

parallel-execution-optimizer

Makes your agent speed up complex tasks by breaking them into smaller parts and running them in parallel. It ensures everything is verified at the end.

affaan-m/ECC