REST Apps

Create an entry for the App that you want to integrate with via REST APIs. You will reference this App for each REST method you will call.

On the main menu, click Apps and at the top-right corner of the page, click Create App and select REST.

The New App page appears. Set the parameters described in the table below.

Parameter

Description

Code

Unique name to identify the App. You will reference in each method you call from this REST App. This field is mandatory.

Type Automatically set to REST. This is a non-editable filed.
Icon

Select the icon that best describes the app. It helps you easily identify the app in the list of apps. If no icon is selected, DRUID default icon per selected app type will be shown in the apps list.

Note:  This field is available in DRUID 1.71 and higher.
Bot Automatically set to the current bot. This is a non-editable filed.
Execution Time

The maximum number of seconds a request is allowed to execute. By default, the timeout for all connector integrations is 60 seconds. This setting will apply to all connector tasks which use this app.

Note:   This field is available for DRUID version 1.60 or higher and requires Connector Host upgrade.
Important!  To avoid long execution time for an integration with many tasks, in DRUID 5.4 and higher, the maximum sum of all timeouts configured on an integration is 250 seconds. Whenever this maximum is reached, the execution of the currently running integration task is interrupted and any subsequent integration tasks are no longer executed.
Encryption Type
Note:   This feature is available in DRUID version 1.61 or higher and requires Connector Host upgrade.

Enables data encryption on the connector using the AES CGM encryption algorithm and allows bot authors to encrypt specific data before sending it to external REST apps, by using the Encrypt Data integration task as first task in the desired connector action.

When you select AES CGM encryption algorithm (the only one currently available), two new options are available:

  • Encryption Key – click the Generate button to generate the key, which will be used by the Encrypt Data task to encrypt the data and by the client / 3rd party application to decrypt the data and use it further.
  • Secure encryption with salt – adds a random 64-bits salt to the data before encrypting it. Please note that using this feature requires the client to develop code for data decryption.

For more information, see Encrypt Data.

Base URL Base URL for all further method calls.
Security Type

When making API calls to external REST services, you can use authentication and authorization to ensure that client requests access data securely.

The DRUID ChatBot Platform allows you to choose from the following authentication methods, which are available in the Security Type drop-down and two separate toggle-ons:

Variables

Integration context variables are specific to connectors and are distinct from DRUID variables used within flows. These variables serve as placeholders for storing sensitive information such as usernames, API keys, and passwords securely.

Upon saving the settings, DRUID encrypts the values, ensuring confidentiality. However, in DRUID version 7.3 and higher, an option is available to exclude encryption if the integration tasks involve consuming non-sensitive metadata.

Important!  
  • Once a variable is encrypted, it cannot be decrypted. Therefore, exercise caution when encrypting variables.
  • When making authorization API calls, refer to the integration context variables using the "@" symbol.