- Search connected data stores using natural language queries
- Return grounded answers with citations from your indexed content
- Support follow-up questions with multi-turn conversations
- Build search-first interfaces with ranked results, filters, and facets
- Inspect which data stores are connected to your Gemini Enterprise setup
Why and when to use it
Use Gemini Enterprise when your organization already uses Gemini Enterprise or Vertex AI Search as the layer that unifies internal data sources. This connector is a good fit when you want Lovable to build on top of that existing search layer instead of calling each source system directly. Gemini Enterprise works best for search and answer experiences such as internal knowledge search, support assistants, and research tools. It is not the right choice when you need direct write access to the source systems themselves, such as sending email, creating Jira issues, or modifying files in external tools.Common use cases and example apps
Requirements and billing
Workspace admins and owners can create Gemini Enterprise connections. Before connecting Gemini Enterprise, make sure you have:- A Google Cloud project with a Gemini Enterprise or Vertex AI Search engine
- Data stores already connected to that engine in Google Cloud
- A Google account that can access the Gemini Enterprise engine and the connected content you want the app to use
- Your GCP project ID
- Your Engine ID
- Your Location (
global,us, oreu) - Lovable workspace admin or owner role
Gemini Enterprise usage, quotas, and billing are managed by Google Cloud. Requests made through this connector count toward your Google Cloud project, not Lovable.
How Gemini Enterprise connections work
- Each connection stores the GCP project ID, Location, and Engine ID for one Gemini Enterprise engine.
- You authorize the connection with a Google account, and Lovable stores that access securely in the connector gateway with automatic refresh.
- Your app can use the connection across linked projects in the workspace.
- You can create multiple Gemini Enterprise connections if you need different engines, environments, or Google accounts.
- For Google Workspace and supported third-party sources connected through Gemini Enterprise, retrieval respects the access of the Google account used for the connection.
- Search results and grounded answers depend on both your Gemini Enterprise engine configuration and the access of the Google account used for the connection.
Setup and configuration
1
Open the Gemini Enterprise connector
Go to Connectors and select Gemini Enterprise.
2
Add a new connection
Click Add connection.
3
Name the connection
Enter a Display name such as
Gemini Enterprise Prod or Internal Search.4
Enter your Gemini Enterprise details
Fill in the connection fields:
- GCP project ID: the Google Cloud project where your Gemini Enterprise engine lives
- Location:
global,us, oreu - Engine ID: the Gemini Enterprise engine identifier
5
Review the requested Google permissions
If you open Advanced settings, you can review the Google permissions requested for the connection. The default selection is appropriate for most Gemini Enterprise setups.
6
Connect and authorize
Click Connect, sign in with Google, and approve the requested access. Lovable verifies that the project, location, engine, and account access are valid before creating the connection.
What to ask Lovable after connecting
Use prompts that make the intended experience clear. Gemini Enterprise supports both classic search interfaces and grounded chat-style answers.Limitations and troubleshooting
- Each connection is tied to the Google account that authorized it. What your app can retrieve depends on that account’s access.
- This connector supports Gemini Enterprise search and grounded answers. It does not expose raw APIs for systems behind Gemini Enterprise, such as Jira REST or Microsoft Graph.
- Gemini Enterprise actions that are only available in the Google Cloud console are not available through this connector.
- Website data stores are not supported for Gemini Enterprise search and assistant apps.
- If you see a 403 error, confirm the Google account can access the engine and the relevant data sources.
- If you see a 404 error, confirm the GCP project ID, Location, and Engine ID exactly match the engine in Google Cloud.
- If you see a 429 error, review quotas and rate limits in your Google Cloud project.
Manage your connection
Connections are managed from Connectors: select , then open the connection.- Unlink projects to remove access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
- Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use stop working until a new connection is added. See Delete a connection for the steps and who can delete.