Integrations allow you to manage a set of Tools belonging to the same API as a single unit, enabling Agents to invoke those actions with a consistent configuration within a Project.
You can access Integrations from the side menu in both the Agentic Hub and the Corporate Hub, where they are labeled Integration Agent Tools. In this view, Integrations are displayed as cards that you can open to review their Tools and configuration.
Within Integrations, you can:
- View and search the Integrations available in your Project.
- Open an Integration and review its configuration.
- Configure shared parameters at the Integration level and specific parameters at the Tool level.
There are two types of Integrations:
- Public Integrations
- Private Integrations
Public Integrations are available by default in all Projects and can be used directly when defining Agents.
A Public Integration maintains its definition in read-only mode. Even in read-only mode, you can configure values within your Project, such as parameters and Credentials, when required by the Integration. Sensitive authentication data is stored as Credentials linked to the Integration.
Some examples of Public Integrations include:
- Web Search: Groups Tools for performing internet searches.
- Code Interpreter: Groups Tools for executing code and returning results.
- Google Drive (Service Account): Groups Tools for accessing and querying files in Google Drive using a Service Account. This configuration is typically used in server-to-server scenarios where access is granted to specific shared folders without requiring end-user authentication.
- Google Drive (User Consent): Groups Tools for accessing and querying files in a user's Google Drive through an OAuth flow. This configuration requires end-user consent and is suitable when the Tool must operate on the user's own Drive files.
- SharePoint: Groups Tools for interacting with files and folders on a SharePoint site.
- Web Scraper: Groups Tools for extracting information from a URL.
For the complete list and details of each, see Public Integrations.
Private Integrations allow you to expose your own capabilities within your Project, such as an internal API.
A Private Integration can contain one or more Tools. Each Tool represents an operation of the API. If several operations must be exposed, the same Integration can include multiple Tools (one per operation), instead of managing them individually.
When Tools are imported, they are created within an Integration.
To create a Private Integration, see How to create a Private Integration.
Integrations support both static and interactive authentication. Configuration is available at the Project level at any time, not only during Agent configuration.
Authentication parameters, including sensitive credentials, are stored at the Integration level and linked to each Integration.
- In static authentication, fixed credentials are configured, and the Tool always executes actions using those credentials.
- In interactive authentication, the Tool obtains authorization during execution, typically through OAuth and the consumer's consent.
An Integration defines common parameters for all its Tools at the Integration level. A Tool can also declare its own parameters. If a Tool is missing expected parameters, review the Integration it belongs to and its linked Credentials.
When a Tool declares a parameter that already exists in the Integration, the value is resolved as follows:
- Inheritance: The Tool declares the parameter but does not define a value, so it uses the value defined in the Integration.
- Override: The Tool declares the parameter and defines a value, replacing the value defined in the Integration.
Migration from Tools to Integrations