So, you provide readability and save time (not spending a considerable amount of time looking at the details and configurations inside your actions) and frustrations.

And sometimes, that may not be enough, and you still need to go to some documentation (API Documentations, project documentation, and so on) to understand.

By setting comments in your actions, you can quickly identify what action is intended for and what is doing, without the need to read all the settings inside the action to try to figure it out.

So, why is it essential to add comments to all our actions? Or at least in the most important ones…Īlmost for the same reasons we describe in the previous Best practices, Tips, and Tricks:

They are not familiar with programming best practices that we can apply to any technology or service like naming conventions addressed previously. But there is also a potential negative impact of empowering citizen developers. Nowadays, citizen developers like business users or end-users can start creating their solutions.

This is quite basic and normal for developers, but once again, Power Automate has a broader audience than typical developers.

Today I’m going to speak about another critical best practice: Comments. In my two previous blog posts, I talked about the most essential best practices you should have while working with Power Automate:

Microsoft power automate desktop ocr