Introducing Flows Web Inputs: New support for user input during a flow run

[Ada Nikolaidis]

Globus Flows now supports Web inputs, a new way for flows to accept user input during a run. Web inputs make it possible to automate workflows with human judgment or approval steps using customizable interfaces directly in the Globus Web App. Additionally, web inputs enforce the high assurance authentication policy associated with a flow.  

Web inputs enable use cases for Flows, such as:

- Requiring explicit sign-off from a designated data steward for transfer to or from a secure enclave

- Allowing review of early experimental results before deciding whether to continue or abort an experiment

- Incorporating curator approval steps into an automated workflow for publishing data

Web Inputs allow a running flow to wait until a designated respondent reviews information and selects a response. Users are notified of pending web inputs that require their response in the user dashboard, can browse their open and closed web inputs, and can submit their response, all without leaving the Globus Web App. 

Web inputs are available to all Globus customers as part of the Flows service. Full documentation is available at docs.globus.org.

If you use the Wait for User Option Selection Action Provider in your flow definition, please update your definitions to use Web Inputs instead. Wait for User Option Selection Action Provider has been deprecated and will be end of life on January 27, 2027. Please contact sup...@globus.org if you need any help with the transition or if you have any questions about using Web Inputs in your flow. 

Ada Nikolaidis
Globus Software Engineering Manager
Globus.org | University of Chicago