Launch Web App

The Launch Web App action enables assignees to open an external URL in order to complete an action in another application. This feature also support advanced automation, enabling you to send data to or receive data from the external application—streamlined processes, reducing manual effort, and saving valuable time. 

Adding Launch Web App to a Flow Template or an Instant Flow:

1. Once you are in the flow builder, locate the desired place where you need the Launch Web App action to be added. 
2. Drag and drop Launch Web App from the left-hand panel under Actions, or click the '+' plus icon between actions in the flow and select Launch Web App.
   
   
   
   

Adding Launch Web App to a Live Flow:

1. Go to the desired flow workspace. 
2. Click on the '...' ellipses icon.
   
   
   
   
3. Select + Add New Action from the dropdown menu. 
4. Then scroll down and choose Launch Web App under Actions.
   
   
   
   
5. Identify the step where you want to insert the new action, and click + Add Here.
   
   

Configuring the Launch Web App action

1. Fill in the following details:
   • Title: Name your request. Choose a title that is descriptive enough for the assignee to understand the action.
   • Description: Add useful details regarding your request.
     • Leverage the DDR (Dynamic Data Reference) by clicking on the ‘{.}’ autofill icon to pull data from workspace details and previous action details.
   • Due Date: Set a due date for this action.
     • Enable the Exclude Weekend option to ensure the due date doesn't fall on a weekend. 
2. Fill in the Web App URL.
   • URL: Enter the Web App URL where the action will take place. 
   • DDR (Optional): Use DDR to automatically fill in relevant data like workspace details and previous action information, by clicking on the ‘{.}’ autofill icon.
   • Button Label: Set the button label that will appear in the action. For example, you can name it 'Review'.
3. Set Additional Options. This is optional.
   • Skip Sequential Order: If enabled, this action can be completed in parallel with the previous action in the workflow.
   • Require Preparation: If enabled, the preparer will need to edit this action before it is ready for assignees.
4. Next, set Assignees.
   • Who needs to access the Web App: Choose the assignee who will be performing this action. 
5. To automate and enhance the action, you can append extra data to the HTTP request made to the external URL. 
   • Append Data - Available parameters include: 
     • Workspace ID: Unique identifier for the workspace where this action belongs.
     • Transobject ID: Unique identifier for this action in the workspace.
     • Assignee Email: The email of the user performing this action.
     • Assignee Name: The name of the user performing this action.
     • Assignee Unique ID: A unique ID assigned by a third-party app.
   • Set HTTP Method
     • GET: Submits data as a query string into the URL. Examples are https://www.url.com?conversation_id=<conversation_id>&transobject_id=<transobject_id>
     • POST: Submits data as form data (key & value) to your app. 
6. Now, you can select how this action should be completed after the user interacts with the web app. 
   • Manual: The user will need to manually click Complete to mark the action as completed after interacting with the external application. You will need to select who should complete this action.
   • Automatic: This will complete the action automatically when the external application sends a webhook to your system. If you select this option, your web application must send a POST request with the necessary payload data to complete the action. 
     • Endpoint: An example is https://smdemo.moxo.com/v1/completeTransobject
     • Payload: A JSON object with conversation_id and transobject_id as the required properties.
       • Example payload is {"conversation_id": "<Workspace ID>", "transobject_id": "<Transobject ID>"}
     • Sample Request
       • Using cURL for a POST request. An example is curl -X POST https://smdemo.moxo.com/v1/completeTransobject -d '{"conversation_id":"BOFHb9PpEy8LnhLfYadXjTL","transobject_id":"22"}' 
       • Basic Authentication (optional): If your web app requires authentication, include the username and password. An example is curl -X POST https://smdemo.moxo.com/v1/completeTransobject -d '{"conversation_id":"BOFHb9PpEy8LnhLfYadXjTL","transobject_id":"22"}' --user "username:password"
7. Before finalizing the Launch Web App action, test the request to ensure everything is set up correctly. 
8. Next, preview and finalize your configuration by clicking Preview. 
9. Then click Add to finalize and add the Launch Web app action to your workflow.