The mobile flows connectors can be customized as per your requirement.

Workspace ONE mobile flows Connector Framework

You can create or add a connector in one the following ways:

  • Use the pre-built connectors developed by VMware to meet specific use cases. These connectors are open-sourced and available on GitHub. See List of Pre-built Connectors.
  • Create custom connectors. The connector framework developed by VMware can be utilized to build mobile flows connectors to meet any use cases, and to support any backend business systems that utilizes RESTful APIs.
  • Add Out-of-the box (OOTB) connectors. See Add Out-of-the-Box (OOTB) Connectors.

For more information on building and installing custom connectors, go to

Building a Connector

You can use the available OOTB connectors or build your own connector. All communication with a connector is over HTTPS. A connector can be written in any language that allows the developer to create HTTP endpoints.

The instructions below provide an overview of the steps you need to follow to build a connector. For information on configuring the connectors from the console, see Configure Connectors from Workspace ONE UEM console.

  1. Add a Discovery API - A connector is registered with Mobile Flows Server by adding a discovery URL. This URL might point to the connector itself, or it might point to static web content (for example, Amazon S3). Discovery tells Mobile Flows Server where to submit object requests, etc. The content behind the discovery is JSON and its
    should be set to
    . Links in discovery served to the Mobile Flows Server must be externally accessible (the Mobile Flows Server must be able to call into the links returned when calling discovery). A common pattern is to be behind a proxy that will fill in X-Forwarded headers that will enable you construct an external URL.
    Note: Discovery resources must be available to unauthenticated clients.
  2. Add a Card Request API to the connector - When a client requests a card, this API is called and a card is requested consists of one or more tokens. These tokens might be pulled from the text of an email (trigger-based card), or they might be from the client's environment, for example, the user's email address.
  3. Return the card response to the client.
  4. Add support for card actions to business systems

Examples of OOTB connectors are available on Github at