Real Agent Cases

Build a Power Automate Desktop flow with Claude Cowork

Posted
by Magic Johnson (@magicj3)
Last checked
Method:
How we verify

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Outcome

After Copilot suggested a subflow that didn't exist in Power Automate Desktop, the poster asked Claude Cowork, which took over and built the flow on their machine.

Agent

Claude Cowork

Prompt Recreated prompt

The source didn't share its exact prompt, so we wrote this from what it describes.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Build this Power Automate Desktop flow for me on my computer.

Check with me first: What should the flow do, step by step?

What I'll give you:
- A description of what the flow should do
- Power Automate Desktop open on my computer

Rules:
- Only use actions that actually exist in Power Automate Desktop.
- If something is missing or unclear, ask me instead of guessing.
- Don't run the flow on real data until I've checked it.

Output: A working flow in Power Automate Desktop plus a short explanation of each step.

You'll know it worked when: the flow runs and does what I described.

Try this in:

Sends the Recreated prompt shown above. ChatGPT and Grok open with it filled in, and ChatGPT may send it straight away. Gemini opens empty, so we copy the prompt for you to paste. Every button also copies it.

The source used Claude Cowork, which can take actions in a browser or app. These are general chat tools, so results may differ, and a normal chat may only give you a plan.

Opens in a new tab. We don't see what you send.

These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.

Optional stronger version

Our rewrite with extra checks. The poster didn't test it.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Build this Power Automate Desktop flow on my computer.

Quick check first: tell me if anything below is missing or unclear.

Inputs (fill in or confirm):
- Step-by-step description
- Apps and files involved
- Test data
- Windows user rights (admin or not)

Rules:
- Use only real PAD actions; name them.
- Add error handling and logging.
- Use variables for paths.
- Test with sample data.
- Write the flow in small subflows with clear names.
- Avoid hard-coded passwords; use PAD's credential or input prompts.
- Add a dry-run mode that logs actions without changing files.
- Document how to change paths and schedule it.
- Confirm each step on screen before running the full flow.

Checkpoint: Ask before running it on real data.

If you get stuck: If an action doesn't exist, propose an alternative. If a login, CAPTCHA or two-step code appears, stop and ask me to handle it; never guess or store passwords.

Verify before you finish: Run the flow end to end on test data.

Output: The flow, notes and test result.

Done when: the flow runs correctly on test data.

Source

https://x.com/magicj3/status/2105499283126407656

  • Build a weekly business KPI dashboard workflow with Claude Code + n8nRecreated promptEvidence: Article or interview

    Claude Code built a complex n8n workflow for a client's weekly KPI dashboard in about 15 minutes; the workflow then runs unattended on n8n.

    Claude Code, n8n · Ops · Source date:

  • Irena Palamani Xhurxhi asked Gemini to build a Google Form. It got partway, then stopped and asked Xhurxhi to take over because it couldn't change the question type in the interface. Xhurxhi gave the same task to Claude in the browser and went back to other work; when they returned, the form was done, with all five questions, correct types, descriptions and required fields. Asked about it, Claude said it had struggled with the same parts, trying clicks, JavaScript workarounds and keyboard navigation, but kept going rather than handing it back.

    Gemini, Claude in Chrome · Ops · Source date:

  • After the poster scanned almost 200 invoices, Claude Cowork split them out, renamed them, sorted them into folders and created a summary Excel file.

    Claude Cowork · Ops · Source date: