Integrations allow you to manage a set of Tools belonging to the same API as a single unit, enabling your Agents to invoke those actions with consistent configuration within your Project.
You can access Integrations from the Side menu in The Lab. In this view, Integrations are displayed as cards, and you can open each one to review its Tools and configuration.
Within Integrations, you can:
- View and search for 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.
Note: As of version 2026-01, standalone Tools were automatically migrated into Integrations. Common parameters moved to the Integration level, and sensitive authentication parameters were converted into Credentials linked to each Integration. When importing, new Tools are created inside an Integration. If you notice missing parameters in a Tool since migration, check its Integration and its linked Credentials. For more details, see
Migration from Tools to Integrations.
There are two types of Integrations:
- Public Integrations
- Private Integrations
Public Integrations are available by default in all Projects, and you can use them directly when defining your Agents.
A Public Integration maintains its definition in read-only mode.
In read-only mode, you can still adjust configuration values within your Project, such as parameters and credentials, when the Integration requires it.
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 for 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 the end-user to grant permission 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.
Note: As of version 2026-01, previous Public Tools from Remote Modules were automatically migrated into Public Integrations. Any sensitive parameters from earlier Tools are now stored as Credentials linked to those Integrations.
Private Integrations allow you to expose your own capabilities within your Project, for example, an internal API.
A Private Integration can contain one or more Tools. Each Tool represents an operation of that API. If you need to expose several operations, the same Integration can include several Tools (one per operation), instead of managing Tools in isolation.
To create a Private Integration, follow How to create a Private Integration.
Note: As of version 2026-01, Previous standalone Private Tools in each Project were grouped into an automatically created Private Integration (1–1).
Integrations support both static and interactive authentication, and the configuration is available for the Project at any time, not just during the configuration of an Agent.
- In static authentication, you configure fixed credentials, and the Tool always executes actions using those credentials.
- In interactive authentication, the Tool obtains authorization during use, typically through OAuth and the end-user's consent.
Note: As of version 2026-01, sensitive authentication parameters that existed at the Tool level were migrated to Credentials linked to the corresponding Integration.
An Integration can define common parameters for all its Tools. A Tool can also declare its own parameters.
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, so it replaces the value defined in the Integration.
Note: As of version 2026-01, common parameters are defined at the Integration level by default. Tools may inherit or override as needed.
Since version 2026-01.