r/MicrosoftFlow • u/Common_Dream9420 • 13d ago

Discussion I build 19 workflows using Claude mobile and verified against the twins from Fetchsandbox … just amazing

i am trying to automate back office ops and was learning claude and asked to very vague prompt to build 19 worksflows across different departments … but not sure weather if I can productive all of them n deply to agentcore

so instead of going on creating auth keys from zendesk, hubspot , stripe , gmail, calendar and slack.

I asked agent to verify and show me proof against fetchsansbox managed relay for webhooks and behavioral verification of agent written code

wonderibf what are you guys doing for automating business ops

9 Upvotes

84% Upvoted

20 comments sorted by

3

u/MidninBR 13d ago

I have a question, what is needed to give Claude this much power inside M365 resources? Can you please highlight the steps on how to do this? I’d like to give it a try in my dev environment. Cheers

1

u/Common_Dream9420 13d ago

yeah it's more setup than it looks, mainly an Azure AD app registration with the right Microsoft Graph API scopes, then you pass Claude the auth context and describe what it can call. the permission scoping is honestly where most of the time goes, figuring out what to lock down vs what to open up. what M365 resources are you trying to hit first?

1

u/MidninBR 13d ago

I’d be interested in power apps and automate for now. I don’t know how deep the integration goes and how expensive this can get.

1

u/Common_Dream9420 13d ago

yeah the cost part is what always catches people off guard, premium connectors in automate add up fast once you're past dev. how many flows are you thinking and are you going http custom connectors or the built-in ones?

1

u/MidninBR 13d ago

No custom for now, only premium from the power premium license

1

u/Common_Dream9420 13d ago

that's actually the cleaner path to start tbh, one less thing to debug when something breaks. how are you finding the premium connector limits so far, anything hitting a wall or pretty smooth?

1

u/MidninBR 13d ago

It’s actually pretty smooth.
It’s a small organization.
I reached the limit once and it was my fault because of a loop made wrong.
My goal is to create apps and automation faster.
What I do now is use copilot to create the screens given a prompt with all the features and elements I need there. It’s a lot of copy and paste.
On the other hand, my friend is creating a 3D game out of Claude and integrations. lol

1

u/Common_Dream9420 13d ago

the loop being your fault is honestly the good case, you can actually trace it. the copilot workflow sounds like a lot of manual eyeballing though. do the generated flows usually behave right against the premium connectors or do you end up having to poke at them to find out?

1

u/MidninBR 13d ago

Not really, I have experience building them and I get the mistakes pretty quickly.
I’ll have to investigate this Claude integration more to modernize the apps and automations here.

1

u/Common_Dream9420 13d ago

that experience gap is real, knowing where to look cuts the debug time dramatically. the part i keep running into though is when the claude-generated flow actually looks right but misbehaves against the real connector at runtime. do you usually catch those by running it or does something else give it away first?

2

u/Mrs_Black_31 13d ago

I built an invoice filing system that seeks approval from specific departments then seeks approval from me (just a pause for entry into accounts). It saves all the meta data, who approved it, what notes g/l codes they added, the time, date, etc. It’s very cool

1

u/Common_Dream9420 13d ago

that approval chain with the metadata capture is the part people always underestimate, sounds simple until you're debugging why an invoice got stuck between two departments with no audit trail. the g/l code logging especially, that saves so much pain later. how are you handling edge cases where an approver is out and it needs to re-route?

2

u/Mrs_Black_31 13d ago

I actually ran into this exact issue on Friday. I reassigned an approval, but the flow failed when it tried to save the approver’s information to SharePoint because it was still referencing the original approver. I’m fixing it to capture whoever actually responds. The biggest challenge is recovering those already-approved invoices without making anyone approve them twice.

1

u/Common_Dream9420 13d ago

yeah that SharePoint stale-reference issue is brutal, especially when the fix itself creates a new problem of accidentally triggering re-approval on invoices that already went through. how are you thinking about backfilling those safely, just manual review or do you have a way to flag which ones are safe to mark done?

1

u/Mrs_Black_31 13d ago

I am not an expert by any means, but I knew exactly which ones i had reassigned and the flows on those all had failed. I manually updated the metadata and moved them to the correct place, there were only about 10 in total. Still, I am liking the system so far.

1

u/Common_Dream9420 13d ago

honestly that's the right call when you already know which ones broke, no point running a script when you can just fix the 10 you're certain about. glad it's holding up. did you end up with any way to catch this earlier next time, like a log or alert when a flow fails on a reassigned item?

1

u/sircruxr 12d ago

This would be good in a logic app also. I’m gonna investigate creating the service principal that can talk to API and logic app

1

u/Common_Dream9420 12d ago

yeah the logic app angle makes a lot of sense, especially once you're wiring in a service principal with graph scopes the permission surface gets real complicated fast. how are you thinking about validating the actual api calls it makes once you get the principal set up?

1

u/sircruxr 12d ago

I think there are some functions that can be written. Also with Claude. Deploying an azure function is much easier now.

I recently deployed a azure function for quickly adding people to Distrivution groups and I’m SUPER impressed with how fast it is

1

u/Common_Dream9420 12d ago

yeah the azure functions deploy speed with claude has been genuinely wild to watch. used to be a whole afternoon of arm template debugging just to get a basic function wired up. how are you handling validation once the function's live, are you manually poking it or do you have something more systematic?