Configure the connector details and map them from within the Workspace ONE UEM console console for the mobile applications to fetch the required details.

The following connectors are provided out of the box that can be configured and deployed to support specific business systems:

Table 1. Mobile flows Connectors

Sample Business System Connector Name

Use Case Addressed


Add a contact to an existing account. Show the user existing contact details.


Approve or reject ServiceNow requests.


Comment on an issue, watch an issue, or open an issue in a browser.

Bitbucket Server

Comment on, approve, decline, and merge Bitbucket Server pull requests.


Comment on, approve, reject, request changes, and merge Github pull requests.


Comment on, approve, reject, and merge Gitlab pull requests.


Approve AWS certificate requests.


Inviting a user to install apps that are missing from the user's device.


Approve an expense report, reject an expense report, and open an expense report in a browser.

Configure Connectors

Once the mobile application fetches the connector details, the device users are provided with an option to enable or disable the Mobile Flows connectors from within the application.

  1. Log in to the UEM Console and navigate to Content>Mobile Flows. If Mobile Flows option is not available in the Content page, check with your Account Manager to purchase VMware Workspace ONE mobile flows add-on.

  2. Select New to create a new connector configuration or Edit to edit an existing connector configuration. Edit Connector page opens.

  3. Select the Name text box and enter the name of the connector that you want to be displayed on the Console and the user's device.

  4. Select the Discovery URL text box and enter the public facing URL for the connector that is deployed within your environment.

  5. Select the Authentication Type drop-down menu and select the required authentication type. Following are the available authentication types:

    1. Basic - User must enter their username and password credentials when enabling connector on their client application.

    2. OAuth 2.0 - The details provided on the console is sent to the client application and the Mobile Flows client framework adds the information to the request header. You must provide additional key values when selecting OAuth 2.0 as the authentication type.

    3. Workspace ONE - The client application on the device uses the Workspace ONE's SSO token for authentication with backend systems.

  6. Select Save.