You can add actions either during data store creation or later. This page provides steps to add new actions after data store creation, and manage the list of actions.
Add actions
Console
To add new actions to the data store, follow these steps:
In the Google Cloud console, go to the Gemini Enterprise page.
In the navigation menu, click Data Stores.
Select a data store of your choice.
From the navigation menu, select Actions.
On the Actions page:
- If actions were not added during data store creation, click Enable actions. Then, on the Enable actions page, to add new actions, do the following:
- For a federated data store:
- Select the actions from the list.
- Click Enable actions.
- For an ingestion data store:
- Expand the Authentication settings section and provide the authentication details.
- Click Login and sign in to the data store to verify your account.
- Click Continue.
- Optional: Expand the Advanced settings and provide the necessary details.
- Select the actions to enable.
- Click Enable actions.
- Expand the Authentication settings section and provide the authentication details.
- For a federated data store:
- To add additional actions to the existing list, do the following:
- Select the actions from the list.
- Click Enable actions.
- If actions were not added during data store creation, click Enable actions. Then, on the Enable actions page, to add new actions, do the following:
To reauthenticate using different credentials than those used for creating the data store, do the following:
- Click Re-authenticate on the Actions page.
- Provide the authentication details.
- Click Login to authorize Gemini Enterprise to access the data store.
- Click Update to update the new authentication details.
To view or edit the data store parameters for actions, do the following:
- Click View/Edit parameters to edit connector-specific details. For example, for Microsoft Outlook, SharePoint, OneDrive, provide the Tenant ID.
- Click Save to update the parameter details.
View actions
Console
To view the list of actions for a data store, do the following:
In the Google Cloud console, go to the Gemini Enterprise page.
In the navigation menu, click Data Stores.
Select the data store of your choice.
From the navigation menu, select Actions. The actions you enabled during data store creation appear as a table on the Actions page.
Disable actions
Console
To disable actions, do the following:
In the Google Cloud console, go to the Gemini Enterprise page.
In the navigation menu, click Data Stores.
Select the data store of your choice.
Select Actions from the navigation menu.
Select the actions to disable from the table.
Click Disable actions.
Manage custom actions
Gemini Enterprise supports custom fields and entities to enable advanced search and actions in data stores. After you create a data store, you can retrieve available operations from your data source and select which ones to expose as actions. To optimize performance, you can also refine the descriptions of each action and its fields for the AI model.
You can use these custom actions in addition to the default actions provided by Gemini Enterprise. To see the actions offered by default, see Supported actions.
You can configure custom actions and fields in the following ways:
- Custom entities: Generate custom actions from the custom entities defined in your data store, and refine the action and field descriptions.
- Custom fields: Modify the existing standard actions by describing how custom fields should be populated.
Before you begin
Ensure that custom entities and operations are configured and exposed by the remote third-party data sources before you attempt to reload actions in the Google Cloud console.
Configure custom actions based on custom entities
You can automatically generate a new set of custom actions based on the custom entities defined in your connected data store.
To generate and enable custom actions:
In the Google Cloud console, go to the Gemini Enterprise page.
In the navigation menu, click Data Stores.
Select a data store.
In the navigation menu, click Actions.
On the Actions page, click Reload custom actions to generate the actions list.
Review the automatically discovered custom actions in the actions list. By default, all newly generated actions are marked as Disabled.
Select the custom actions that you want to make available.
Click Enable actions. The status is marked as Enabled for the selected actions.
Click Save.
Optional: To improve the user experience, enrich the action and field descriptions in the specification:
- On the Actions page, select an action whose specification you want to modify.
- Click Download specification to download the specification JSON file.
- Open the downloaded JSON file in a text editor and modify the descriptions and data types in the
inputSchema. For example, you can add an instruction such as "Always default to 10" to a parameter description. - In the Google Cloud console, click Upload specification to upload the updated JSON file. The specification file is validated for basic syntax errors.
- Click Save.
Configure custom fields for standard actions
For some data stores, standard actions are provided automatically, and custom field support is enabled by default during data store creation. However, you can explicitly define how the model should handle specific custom fields by modifying the tool specification.
To update a standard action with custom field definitions:
In the Google Cloud console, go to the Gemini Enterprise page.
In the navigation menu, click Data Stores.
Select a data store.
In the navigation menu, click Actions.
Click Manage specification.
Select the standard tool or action that you want to update.
Click Download specification to download the specification JSON file.
Open the downloaded JSON file in a text editor and add your custom field definitions, descriptions, and data types to the
inputSchema.In the Google Cloud console, click Upload specification to upload the updated JSON file. The specification file is validated for basic syntax errors.
Click Save.
Limitations
If your refresh token expires, enabling custom actions might fail with an error, or the actions might not appear as enabled. To resolve this issue, reload the Actions page or re-authorize the connected app to refresh your token.