Showing results for 
Search instead for 
Did you mean: 

Ask user for input

There should be a way to send an email asking somebody to input something. This input could be used as dynamic content. It would be nice to allow a user to change a variable. For example, asking a user what time something should be or giving the option to change a time. It would also be nice if there was a comment box for email with options. Personally, that would solve my issues, but I feel like a general "Ask user for input" could be more valuable for its wide variety of uses.

Status: Under Review

The recommended way to do this is to use approval flows. These can receive input from users and then proceed based on the selected input. 

Advocate IV

This is a terrible gap. Nintex has such feature back in 2007!!!


We need to have a user provide a "string"  or "integer" and not have to select from a pre-defined options.  This lack of (easy to implement) feature is causing all sorts of problems in our effort implement more automation.


We need people to input a quantity, or a specific word on many occasions... 

Advocate I

@Stephen, I agree the approval workflow can get text inputs from user, but it is specific to approvals only. I don't feel comfortable using this action when I have get an input from the user without involving any approval because the approval email header clearly says it is an approval request. It would be great if the approval email header could be generic or configurable so it didn't look like it is requesting approval in all cases.


Hope this makes sense. Thank you. 

New Member

You can create a workaround if you combine your Flow with Siri Automations on an iPhone. It's a bit of hack as the Automation has to be setup on each users iPhone locally. But essentially, it does the trick. Once the flow started running it will send an email to your user, which will then trigger a Siri Automation and ask for an input. The input is sent back to Power Automate via email and once received, a second flow is triggered, which now can store the users input in a variable. You can read more about said workaround here (although in German):