Luma Automations Serviceaide Automation supports integration with any third-party applications that support REST APIs to execute tasks on the target system. The Integration enables the workflow to connect to a target system and perform a task. Workflow Developers can configure the APIs and connect to the target system to retrieve data or perform an action. These integrations can be added in sequence as steps to design a business process workflow. Here we configure the system details, authentication credentials, and mechanism for the connection.
Follow the below steps to create an Integration:To integrate with a third-party system, you should do the following:
...
Create App
To create an app'Connected Apps' represent the third-party applications that are the endpoints in a workflow. The integrations are defined at the tenant level with connectivity and authentication mechanism details, that are used by the Automation workflow to connect to the target system. A Workflow developer can create REST operations that are supported by the target applications.
To create an application, follow the below steps:
Navigate to Integrations in the left panpane.
The Connected Apps page appears as shown below. All the existing connectors are available here. These are available throughout the tenant and can be used in various workflows.
To create a new integration, click on Create App. The Create App page appears as shown below.
Enter the App Name. This represents the target system where you want to execute the task.
Select the Integration Type based on the type of integration supported by the target system. For REST connectors, select REST Integration type.
Add an App Icon.
Add a Description.
Click Create to complete the App creation.
The created app is now available in the Connected Apps list.
...
Once the Connected App is created, the The next step is to create the Instance.
| Info |
|---|
For Mule Connectors, select 'Mulesoft' as the integration type. For more information on creating Mule connectors, refer to Importing Mulesoft Connectors. |
Create Instance
Instance An instance represents the system environment you want to connect to. For , for example, For an Application (a configured target system), you may add a Trail Environment and a Production environmentTrial, Production, Staging etc. The App Instance helps to set the target environment for the execution of the web service operations. Here, you may provide can define the Request configuration configurations such as the Global Path parameter, Global Request Header, Global Query parameter, and authentication details required for Instance configuration and connecting to the target system. These are the default configurations for the instance but can be over-ridden at the Web Service The task is executed on the instance is selected in the Workflow. The configurations at the instance are global and can be overridden at the Operations level.
To create an instance, follow the below steps:
On the Integrations page, select the required Application and click on Create Instance as shown below.
The Create Instance page appears.
Enter the instance Name. The next step is to define the credentials and connection details for this instance.
In the Instance Configuration section, Enter the base URL to the target system environment where the task should be executed.
The Authorization Type is used to log in and perform the task. The Following are the supported authorizations types:
No Auth: Use this option, if you do not need any authentication to log in to the third-party systems.
Basic Auth: Use this option if the target system needs login credentials to authenticate and authorize the user. ‘Basic Auth’ consists of the following fields:
Username: Specify the Username used to log in to the third-party system.
Password: Specify the password used to authenticate access to the third-party system.
Bearer Token: This is the unique authentication token required for external applications to communicate with Luma Automation. Enter the unique authentication Token required for external applications to communicate with the Automation Workflow.
Global Path Parameter: The path parameter is part of a path segment that occurs after its name. Path parameters offer a unique opportunity to dynamically replace the values and pass them in the URL. Example, http://myserver.com/some-path/{parameter1}/path-continued/{parameter2}.
Enter the External Field and the Value.
Global Query Parameter: The query parameters are sometimes referred to as optional parameters. The query parameters are separated from the hierarchical parameters by the question mark. Query parameters appear in the URL after the question mark (
?) after the resource name. Example, https://myserver.com/resource-name?param1=value1¶m2=value2.Enter the External Field and the Value.
Global Headers: Headers are mostly classified as Request Headers. You will have to set the request headers when you are sending the request.
Enter the External Field and the Value.
The following sample headers are encountered the most.Authorization: Includes credentials containing the authentication information of the client for the resource being requested.
Accept-Charset: This is a header that is set with the request and tells the server which character sets are acceptable by the client.
Content-Type: Indicates the media type (text/HTML or text/JSON, XML/custom) of the response sent to the client by the server, this will help the client in processing the response body correctly.
Click Create to create the App Instance.
| Info |
|---|
|
Operations
Operations are the actions, performed on the target system. These represent the functions that are exposed by the Target system’s API. As a Workflow designer, you can configure operations that can be added to the workflows to perform a specific task in the target environment.
There are two ways to create REST Operations for your Workflow:
Global Operations- Operations created at the tenant level and can be used in any workflow.
Workflow specific Operations- Operations created during workflow designing