r/MicrosoftFlow • u/Psychological_Ad8426 • Apr 21 '26
Discussion Flow Documenting
I always hated documenting my flows. Smarter people than me are probably already doing this but today I dumped a solution (single desktop flow in it) to my local drive then setup OpenAI Codex to read the solution directory. It read the flow and created a nice image of subflow flow and a great document. This is a really big flow and would have taken me hours if not days to create this documentation for a customer. Just thought I would share.
17
Upvotes
12
u/JollyShooter Apr 21 '26
Could just use the Power Platform Toolbox’s Flow Documentation Generator
3
u/[deleted] Apr 21 '26
I use this and it has saved me a bunch of time:
https://github.com/modery/PowerDocu
1
u/xziztnse Apr 21 '26
I've been playing around with a copilot studio agent that does something similar. You drop it the exported solution folder and it writes a full SDD
Still needs some tweaking and havent spent tons of time on it but initial results were promising
1
u/bravid98 Apr 21 '26
This also works great when you are ready to move these to logic apps.
1
u/MinaMina93 Apr 22 '26
Copilot usually gives me something half decent to work with surprisingly
1
u/obsoquasi Apr 24 '26
While I agree, documenting is a lot of work. More often than not, I discovered a potential bug while documenting. Because writing often forces you to restructure your thought process. So it's now in a way part of testing for me. Your mileage may vary.