Google Bard v1.0.0

About the connector

Google Bard is a conversational AI chatbot, based initially on the LaMDA family of large language models and later the PaLM LLM.

This document provides information about the Google Bard Connector, which facilitates automated interactions, with a Google Bard server using FortiSOAR™ playbooks. Add the Google Bard Connector as a step in FortiSOAR™ playbooks and perform automated operations with Google Bard.

NOTE: This connector has been renamed to Google Gemini. For subsequent updated versions of this connector, refer to Google Gemini connector documentation.

Version information

Connector Version: 1.0.0

FortiSOAR™ Version Tested on: 7.4.1-3167

Google Bard API Version Tested On: v1beta2

Authored By: Fortinet

Certified: Yes

Installing the connector

Use the Content Hub to install the connector. For the detailed procedure to install a connector, click here.

You can also use the yum command as a root user to install the connector:

yum install cyops-connector-google-bard

Prerequisites to configuring the connector

• You must have the credentials of Google Bard server to connect and perform automated operations.
• The FortiSOAR™ server should have outbound connectivity to port 443 on the Google Bard server.

Minimum Permissions Required

• Not applicable

Configuring the connector

For the procedure to configure a connector, click here

Configuration parameters

In FortiSOAR™, on the Connectors page, click the Google Bard connector row (if you are in the Grid view on the Connectors page) and in the Configurations tab enter the required configuration details:

Actions supported by the connector

The following automated operations can be included in playbooks and you can also use the annotations to access operations:

operation: Get All Model List

Input parameters

Output

The output contains the following populated JSON schema:

{
    "models": [
        {
            "name": "",
            "topK": "",
            "topP": "",
            "version": "",
            "description": "",
            "displayName": "",
            "temperature": "",
            "inputTokenLimit": "",
            "outputTokenLimit": "",
            "supportedGenerationMethods": []
        }
    ],
    "nextPageToken": ""
}

operation: Get Model Details

Input parameters

Output

The output contains the following populated JSON schema:

{
    "name": "",
    "topK": "",
    "topP": "",
    "version": "",
    "description": "",
    "displayName": "",
    "temperature": "",
    "inputTokenLimit": "",
    "outputTokenLimit": "",
    "supportedGenerationMethods": []
}

operation: Generate Text

Input parameters

Output

The output contains the following populated JSON schema:

{
    "candidates": [
        {
            "output": "",
            "safetyRatings": [
                {
                    "category": "",
                    "probability": ""
                }
            ]
        }
    ]
}

operation: Generate Embedding

Input parameters

Output

The output contains the following populated JSON schema:

{
    "embedding": {
        "value": []
    }
}

operation: Count Message Token

Input parameters

Output

The output contains the following populated JSON schema:

{
    "tokenCount": ""
}

operation: Generate Message

Input parameters

Output

The output contains the following populated JSON schema:

{
    "messages": [
        {
            "author": "",
            "content": ""
        }
    ],
    "candidates": [
        {
            "author": "",
            "content": ""
        }
    ]
}

Included playbooks

The Sample - Google Bard - 1.0.0 playbook collection comes bundled with the Google Bard connector. These playbooks contain steps using which you can perform all supported actions. You can see bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Google Bard connector.

• Count Message Token
• Generate Embedding
• Generate Message
• Generate Text
• Get All Model List
• Get Model Details

Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during connector upgrade and delete.