Workspace ONE mobile flows connectors can be customized to your requirement.

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 must follow to build a connector. For information on configuring the connectors from the console, see Configure Workspace ONE mobile flows Connectors from the Workspace ONE UEM Console.

  1. Add a Discovery API - A connector is registered with the 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 the Mobile Flows Server where to submit object requests. The content behind the discovery is JSON and its 
    Content-Type
    must be set to 
    application/json
    . 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 fills in X-Forwarded headers that 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 https://github.com/vmware/connectors-workspace-one.