Flow Studio Blog

Power Automate Work Order Automation: Email + PDF to Excel

catherine.han@flowstudio.app (Catherine Han) — Sat, 09 May 2026 13:51:05 GMT

Best way to automate Outlook emails + PDF work orders into Excel? (n8n / Power Automate) A property maintenance company asked on r/MicrosoftFlow this week. The OP listed the failure modes that kept biting them: inconsistent email formats, PDF extraction problems, Excel append failures, table and column mapping issues, sometimes Outlook body content getting truncated. The follow-up question I had was the more interesting one: AI Builder, Copilot Studio with Work IQ Outlook, or build it yourself?

So I screenshotted the post and sent it to my Telegram bot. I was lying on the bed on a Saturday afternoon, no VS Code, no Power Automate designer, no Azure portal. On the other end of the Telegram chat is a Claude PM running TmuxAgentManager, which dispatches the build to a Codex worker in a tmux session. About two and a half hours later I had a two-flow Power Automate solution writing to Excel with a confidence-gated exception path.

The useful pattern is to combine the email body and the PDF text into one context, extract once, and use a confidence score to decide whether the record goes straight into operations or into an exception queue for human review.

What follows is the field note the Codex worker wrote, lightly edited. What I personally validated: the test emails landed in my Outlook with their PDF attachments, both flows ran in the Power Automate run history, and the extracted rows landed in WorkOrder_Operations.xlsx with the fields populated. Demo worked end to end. Great work to the worker, to the PM for keeping it on rails, and to Flow Studio MCP for giving the worker action-level visibility into every Power Automate run, which is what made the silent-failure debugging in sections [05] and [06] tractable.

The next section is written from the worker's point of view. I kept the engineering detail because the failure modes are the useful part.

Codex Agent Builds Power Automate Flow for Distribution List Owners

catherine.han@flowstudio.app (Catherine Han) — Tue, 28 Apr 2026 09:17:02 GMT

Can we fetch the owner of a distribution list in Power Automate? A question on the Power Platform community forum this week. The kind that sounds like it should be a one-step connector call, until you realise classic Exchange distribution lists do not show up cleanly through the standard Power Automate or Microsoft Graph paths.

So I handed it to my Codex agent in VS Code.

What follows is the field note the agent wrote about the build, lightly edited for length. Most of the work happened inside an Azure Automation runbook, and I am going to be honest: that is not my home turf. I am not going to pretend I read every PowerShell line it wrote. What I did do is:

1. create a test distribution list and assign myself and a test account as owners
2. grant the Entra role when prompted by the agent
3. check the finished flow run triggered by the agent, and confirm the JSON came back with both owners correctly resolved.

That is enough for me to say the solution is solid. Great work to the agent.

Though, this is not a no-permission maker workaround. It is an IT-approved pattern for cases where Power Automate needs Exchange Online PowerShell to get the data reliably.

Publish SharePoint Pages from a Copilot Studio Agent with a Power Automate Dispatcher Flow

catherine.han@flowstudio.app (Catherine Han) — Mon, 27 Apr 2026 15:56:20 GMT

How do I document my Power Automate flows? Same forum question as Posts 1 and 2, third answer.

This is the third version of the same documentation pattern. The output is now a real SharePoint Site Page per flow, plus a row in FlowDocsInventory. The agent still reads the flow definitions through Flow Studio MCP, but it publishes pages through a Power Automate dispatcher flow instead of writing SharePoint pages directly.

Post 1 used an IDE and a service principal. Post 2 stayed in Copilot Studio but produced Word docs in a document library, because Work IQ SharePoint can't write Site Pages. This post fills that gap. The agent does not get open-ended SharePoint write access; it gets one approved flow with eight named operations.

The meta detail: I had the agent build the dispatcher flow itself, using Flow Studio MCP. Same agent, same MCP server, used in the other direction. Reading flows on the way in, writing a flow on the way out.

Document Power Automate Flows in Copilot Studio with Work IQ

catherine.han@flowstudio.app (Catherine Han) — Mon, 27 Apr 2026 13:55:48 GMT

How do I document my Power Automate flows? Same forum question as Post 1, second answer.

Post 1 showed the developer path: an AI coding agent in an IDE, plus a SharePoint service principal. Fast if you have that setup. Not useful if you want the work to happen inside Microsoft 365.

This post is the no-IDE version. One Copilot Studio agent, two tools, and the same documentation spec: 6 inventory columns and 7 sections per flow.

I didn't open Power Automate designer, the SharePoint admin centre, or Azure once.

Auto-Document Power Automate Flows with Claude or GitHub Copilot

catherine.han@flowstudio.app (Catherine Han) — Mon, 27 Apr 2026 10:19:56 GMT

How do I document my Power Automate flows? It comes up in every Power Platform community forum I read. It is a real pain for the people responsible for flows. Very few people enjoy reading through old flows and turning them into documentation.

Nowadays with GPT this has been easier - many people throw the definition into GPT and ask it to summarize the flow. But it is still manual - you need to do it flow by flow.

I have three autonomous approaches with MCP that resolve the problem in bulk. Even if you have hundreds of flows, these approaches won't take you more than a half day to document the first draft (assuming human review final outcome would still take time). With the MCP free quota, <70 flows is likely to be completely free.

This article is the first of the trilogy - this is the developer path: an AI coding agent in your IDE writes the docs, you review and ship.

I didn't open Power Automate designer once.

Monitor a Webpage in Power Automate Without Premium: The IMPORTHTML Trick

catherine.han@flowstudio.app (Catherine Han) — Thu, 23 Apr 2026 14:33:53 GMT

How a Reddit question became a one-hour exercise in knowing when to pivot.

Updated 2026-04-24: The OP came back with a tighter constraint — their tenant is Office-Online-only, no Google Workspace. That sent the agent and I back to the drawing board and we found two cleaner paths: OneDrive's "Upload file from URL" action, and GitHub's per-file ATOM feed. Scroll to the bottom for both.

A community member asked on r/PowerAutomate:

Is there a reliable way to monitor a webpage section (like a table) using only standard connectors? I want an email whenever a new SQL Server 2025 GDR build is published on this Microsoft Learn page. No premium, no SSMS, converting to RSS couldn't isolate the GDR section reliably.

So I handed the problem to my agent — Claude Code + Flow Studio MCP — and gave it the brief: standard connectors only, which rules out the HTTP action that would normally solve this in ten minutes.

Here's what the working solution looks like, and more interestingly, the two wrong turns the agent took to get there.

How to Connect a Custom MCP Server to Copilot Studio to Debug Power Automate

catherine.han@flowstudio.app (Catherine Han) — Wed, 15 Apr 2026 14:06:20 GMT

Copilot Studio supports custom MCP servers as tools. This post shows how to connect Flow Studio MCP to a Copilot Studio agent so it can debug Power Automate flows at the action level: read per-action error breakdowns, inspect action inputs and outputs including loop iterations, and trace root causes back to source data. Five-step setup inside Copilot Studio, no code. Includes a real debug session with every MCP tool call visible on screen.

Microsoft 365 Copilot, calling get_live_flow_runs on a real Power Automate flow. Inspecting action inputs and outputs at the trigger level. Printing a per-flow verdict table that traces root causes back to the source data.

This is not a standard Copilot Studio capability. Plain Copilot Studio has no action-level visibility into Power Automate. Microsoft shipped Model Context Protocol (MCP) server support in Copilot Studio (public preview March 2025, generally available May 2025 at Build), so you can plug in a custom MCP server and give the agent exactly the tools it's missing. The one in this post is Flow Studio MCP, a Power Automate MCP server I built. It exposes about 15 tools covering environments, flow definitions, run history, action inputs and outputs, connections, and deploy operations.

This post covers three things. First the 5-step setup inside Copilot Studio. Then a real debug session with the tool calls visible. Then what your end users see once the agent is published to the Microsoft 365 Copilot app on their machine.

I Built a Flow That Fixes Failed Power Automate Flows | Copilot Studio + MCP

catherine.han@flowstudio.app (Catherine Han) — Sun, 12 Apr 2026 10:55:15 GMT

A failed flow sends an HTTP trigger. A Copilot Studio agent reads the run history, produces a plain-English diagnosis, and sends it for human approval. If the reviewer asks for a fix, the agent proposes one. If the reviewer approves it, the agent applies the fix, redeploys the flow, and resubmits the failed run to verify the result. All inside Power Automate.

This pattern only became practical once agents could inspect action-level run history programmatically instead of relying on run-level status alone.

This post walks through the approval-gated pattern behind it. The point is not full delegation. The point is controlled delegation.

Disclosure: We built Flow Studio MCP, the MCP server the agent uses to read action-level Power Automate data. The architecture pattern generalizes to any MCP server, but the specific tools referenced here are ours.

I Told a Reddit User to Stop Learning Power Automate. Here's Why in 2026.

catherine.han@flowstudio.app (Catherine Han) — Sat, 11 Apr 2026 14:23:00 GMT

Yesterday a one-person business owner posted on r/PowerAutomate asking whether it was worth investing the time to learn Power Automate and SharePoint. They're on Mac, working mobile-first. They're running 50 active projects and already drowning in administrative work. Power Automate didn't stick when they tried it once, and they ended up paying for a third-party tool called relay.app for the one automation they got working.

What they really wanted to know was whether it was worth slogging through the learning curve, or whether they should just pay for yet another tool and accept the sprawl of eight monthly subscriptions. My answer was - do not learn it.

Disclosure up front: I replied to that thread because we build Flow Studio MCP, a Power Automate MCP server that fits exactly this situation. Take my advice for what it's worth, knowing I'm not disinterested.

AI Agent Built My Power Automate Flow: 80 Actions Down to 17

catherine.han@flowstudio.app (Catherine Han) — Mon, 16 Mar 2026 12:30:33 GMT

Sharing my experience from the past two days using an AI Agent + MCP to build a Power Automate flow for a client.

The client's request

The client needed document processing automation. When someone uploads a Word report to a SharePoint list, Power Automate converts it to PDF, saves it to the right document library, sends a Teams message, and sends an email. Different document types go to different locations and different channels.

They already had a working flow for 3 document types, using Switch blocks to route each type. I needed to build a new one for another team, this time with 6 document types.

So I thought: why not just have the AI agent build it for me.