If I get that correct, you need the Account of the current user in your microflow to do something with it.
The $CurrentUser is an object that is always avalable in a microflow. The only problem is, it is not an account. But you can cast it using an inheritance split and a cast action. This will give you the account.
You can use a submicroflow like this one:
You probably want to remove the Account parameter from the microflow and retrieve it in the microflow itself.
Hope this helps.
Or like Andreas suggested… if you create a submicroflow for this, you can easily reuse it.
Ok guys. I’m going to try Andreas idea because I do agree with the fact that account is normally in the memory and no db action is needed to get the info.
If I don’t succeed I’ll ty your Micha.
I did the Andrea s way and worked perfectly !