﻿---
title: Google Gemini connector and action
description: Documentation for the deprecated Google Gemini connector, used to send requests to Google Gemini models from Kibana.
url: https://docs-v3-preview.elastic.dev/elastic/kibana/pull/303145/reference/connectors-kibana/gemini-action-type
products:
  - Kibana
applies_to:
  - Elastic Cloud Serverless: Deprecated
  - Elastic Stack: Deprecated since 9.5
---

# Google Gemini connector and action
<important>
  This connector is being replaced by Elasticsearch inference endpoints and will be removed entirely in Elastic Stack 10.0 or in January 2028, whichever comes first. To configure access to an LLM provider, create an inference endpoint with the `chat_completion` task type. For steps that use your own provider account and API key, refer to [External inference](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/explore-analyze/elastic-inference/external). To use models that Elastic hosts instead, refer to [Elastic Managed LLMs](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/303145/reference/connectors-kibana/elastic-managed-llm).Availability of this connector depends on your deployment and version:
  - <applies-to>Elastic Cloud Serverless: Deprecated</applies-to> <applies-to>Elastic Stack: Planned for deprecation</applies-to> You can no longer create new connectors of this type by selecting **Create connector** in Kibana. Existing connectors and their rule actions continue to work, but the **Connectors** page hides them by default. To show them, open **Display options** and set **Deprecated** to **Show**.
  - <applies-to>Elastic Stack: Deprecated in 9.5</applies-to> This connector is still available, but deprecated.
</important>

The Google Gemini connector uses [axios](https://github.com/axios/axios) to send a POST request to Google Gemini.

## Create connectors in Kibana

<applies-to>
  - Elastic Cloud Serverless: Unavailable
  - Elastic Stack: Planned for removal
  - Elastic Stack: Deprecated in 9.5
</applies-to>

You can create connectors in **Stack Management > Connectors**.

### Connector configuration

Google Gemini connectors have the following configuration properties:
<definitions>
  <definition term="Name">
    The name of the connector.
  </definition>
  <definition term="API URL">
    The Google Gemini request URL.
  </definition>
  <definition term="Project ID">
    The project which has Vertex AI endpoint enabled.
  </definition>
  <definition term="Region">
    The GCP region where the Vertex AI endpoint enabled.
  </definition>
  <definition term="Default model">
    The GAI model for Google Gemini to use. Current support is for the Google Gemini models.
    - <applies-to>Elastic Cloud Serverless: Generally available</applies-to> Defaults to `gemini-2.5-pro`.
    - <applies-to>Elastic Stack: Generally available since 9.1</applies-to> Defaults to `gemini-2.5-pro`.
    - <applies-to>Elastic Stack: Generally available since 9.0</applies-to> Defaults to `gemini-1.5-pro-002`.
      The model can be set on a per request basis by including a "model" parameter alongside the request body.
  </definition>
  <definition term="Credentials JSON">
    The GCP service account JSON file for authentication.
  </definition>
</definitions>


## Test connectors

You can test connectors as you're creating or editing the connector in Kibana.
The Google Gemini actions have the following configuration properties.
<definitions>
  <definition term="Body">
    A stringified JSON payload sent to the Google Gemini invoke model API. For example:
    ```text
    {
      body: JSON.stringify({
            contents: [{
                role: user,
                parts: [{ text: 'Hello world!' }]
            }],
            generation_config: {
                temperature: 0,
                maxOutputTokens: 8192
            }
      })
    }
    ```
  </definition>
  <definition term="Model">
    An optional string that overwrites the connector's default model.
  </definition>
</definitions>


## Connector networking configuration

Use the [Action configuration settings](/elastic/kibana/pull/303145/reference/configuration-reference/alerting-settings#action-settings) to customize connector networking configurations, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use `xpack.actions.customHostSettings` to set per-host configurations.