Agents can use Tools from Integrations during execution. In addition to the Public Integrations available by default, you can define Private Integrations in your Project.
This step-by-step guide explains how to create and test a Private Integration.
First, log in to Glob.AI OS. In the Navigation header, select the Organization and Project you want to work with. In this case, Demo is used as the Organization and Documentation as the Project.
Next, on the left side of the screen, locate the side menu and select one of the following options:
The Integrations Dashboard opens in the central working area. By default, it displays both Public and Private Integrations available in the Project. Public Integrations do not display the More Options link on the card.
To create a new Private Integration, click on the + Import Integration button in the upper-right corner.
Clicking + Import Integration opens the Import Integration dialog.
In this dialog, select the file that defines the Integration:
- Click on Upload or drag the file to the Select File area.
- After selecting the file, click on Read file.
The Lab supports JSON definitions based on OpenAPI and MCP. In this case, the Weather API is used.
After the file is read, the Integration Name field is filled with a suggested value based on the file contents. You can keep the suggested value or modify it. The Description field is optional. You can add a short text describing the purpose of the Integration.
When you finish adjusting these values, click on Continue.
After the process completes, a confirmation message indicates that the Integration was imported successfully. From here, you can import additional definitions or select Edit Integration.
Clicking on Edit Integration opens the Integration in a new tab. This page is organized into the following sections:
- 3.1. Details
- 3.1. Security Scheme
- 3.2. Integration Parameters
- 3.3. Tool Parameters
In the Details tab, define the basic information of the Integration.
Here you can:
- Review or modify the Name suggested from the imported file.
- Optionally provide a Description summarizing the Integration purpose.
- Optionally upload an Integration Icon to represent the Integration. SVG format at 24x24 px is recommended.
In Security Scheme, configure the basic information and authentication settings for the Integration.
Here you can:
- Select an Authentication Level (for example, Project or User).
- Choose the Authentication type: None, API Key, or OAuth, according to the external service requirements.
In this case, authentication is not required, so Authentication type = None.
The Integration Parameters Tab defines configuration and connection values that apply to the entire Integration and are shared by all its Tools.
When no parameters are defined, the tab displays an empty state. If the Integration requires shared values (for example, credentials or project-wide configuration), click on Add new parameter to create them.
Each Integration parameter includes the following fields:
- Key: Identifies the parameter.
- Type: Indicates how the value is provided (for example, Config).
- Value: Stores the value used in the Project.
- Data Type: Defines the expected data type (for example, String).
- Required: Indicates whether the parameter is mandatory.
- Secret: Marks values that must be stored securely (for example, API keys).
For the WeatherAPI Integration, it is not necessary to define Integration parameters, so this tab can remain unchanged.
The Tool Parameters Tab lists the Tools included in the Integration and the parameters specific to each one.
Each Tool appears as a collapsible panel identified by its name. For Integrations imported from an OpenAPI definition, the Tool name is generated automatically based on the Integration and the operation name (for example, weather-api_checkweatherusingget_get). This value does not need to be modified or configured in this view.
When expanding a Tool, you can:
- Review the Tool description.
- Configure the parameters required for execution, such as input fields or operation-specific options.
Each Tool parameter includes fields such as Key, Type, Value, Data Type, Required, and Secret, following the same structure used in Integration Parameters.
In the WeatherAPI Integration, the weather-api_checkweatherusingget_get Tool exposes an Application parameter called location that defines the place for which weather information is requested. Its value is dynamically filled at runtime based on end-user input.
After the Integration is imported and configured, it becomes available in the Project.
From the AI and Tools Tab of an Agent, you can:
- Enable the Tools belonging to the Integration.
- Combine them with other Tools required by the Agent.
Any configuration defined in Integration Parameters and Tool Parameters is applied when the Agent invokes these Tools during execution.