About the Google Gemini category

o.plokha · October 1, 2024, 9:37am

Put topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.

Extra information

System documentation: Google Gemini API Reference

Connector package documentation

1. Setting up HTTP Client Google Gemini

1.1 Steps

In the Alumio Dashboard, go to Clients → HTTP Clients. Create a new HTTP Client.
Select Google Gemini HTTP Client as PlatForm and click next step
Fill in the Gemini API Keys.
(See the Google Gemini Authentication Documentation for more information)
You can optionally enable logging of request to get the log of the authentication.
Click next step, fill the name of the HTTP Client and finally you can save the HTTP Client for use.

2. Subscribing to Entities from Google Gemini

2.1 Steps

Go to Connections → Incoming and create a new incoming configuration and select “Google Gemini Subscriber” as the subscriber.
Select the Method that you want the subscriber to get the data.
Select the entity you want to subscribe to from Google Gemini.
Add any request parameters needed to subscribe to the entity.
Select the Google Gemini HTTP Client to use.
You can optionally add a transformer to transform the request parameters into something you will request from Google Gemini.
You can also optionally enable pagination to allow Alumio fetches paginated entities.

2.2 General Concept

We follow Google Gemini documentation on building this connector, so you can easily use the connector based on Google Gemini API Reference.

Entity

The entity you want to subscribe to Google Gemini. Please refer to the entities from Google Gemini API Reference page.

Request Parameters

These are the parameters you can provide to get the needed entity based on the Google Gemini API Reference.

Please look at the example below on how to fill path field when we want retrieve list comments by subscribing “Method: models.get” entity.

From the end point, we can see that we need to set the model as parameters. That is why we set the “model” inside the path key in the Request Parameters.

Alumio will then make a request to Google Gemini with the URL https://generativelanguage.googleapis.com/v1beta/gemini-1.5-flash-latest

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0
Payload is the data contained within a request.

HTTP Client

The HTTP Client configuration you will use to access Google Gemini.

3. Publishing Entity to Google Gemini

3.1 Steps

Go to Connections → Outgoing, create a new outgoing configuration and select “Google Gemini Publisher” as the publisher.
Select the Method that you want the publisher to perform with the data.
Select the Google Gemini entity you want the data to be published to.
You can optionally add any query data to the request on the key query.
You can optionally add any payload data to the request on the key payload.
Select the HTTP Client to use.

3.2 General Concept

Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration), though you can also add or modify payload using the Request Transformer.

Method

Currently, we support HTTP Post method, HTTP Patch method and HTTP Delete method on submitting data to Google Gemini.

Entity

We support publishing to most Google Gemini endpoints.
Please refer to Google Gemini API Reference page.

For example, we want to generate content by a model. Please select “Post” as the Method and “Method: models.generateContent”.

From the documentation, we can see that we need to set a path parameter and a body parameters. That is why we set the “model” inside the path key and body parameters inside the payload key in the data.

Alumio will send an API request to Google Gemini with URL https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-flash-latest:generateContent

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0
Payload is the data contained within a request.