composio-google
Adapts Composio tools to the Vertex AI SDK (vertexai.generative_models) as FunctionDeclaration objects for Gemini function calling.
Installation
pip install composio composio-google google-cloud-aiplatform
Set COMPOSIO_API_KEY (create one at https://dashboard.composio.dev/settings) in your environment. Vertex AI authenticates with Google Cloud credentials; run gcloud auth application-default login or set GOOGLE_APPLICATION_CREDENTIALS.
Quickstart
GoogleProvider is non-agentic: the model returns function calls, and composio.provider.handle_response executes every function call in the response through the session and returns the results.
import vertexai
from vertexai.generative_models import GenerativeModel, Tool
from composio import Composio
from composio_google import GoogleProvider
vertexai.init(project="your-gcp-project", location="us-central1")
composio = Composio(provider=GoogleProvider())
# Create a session for your user
session = composio.create(user_id="user_123")
tools = session.tools()
model = GenerativeModel(
"gemini-3.7-flash",
tools=[Tool(function_declarations=tools)],
)
chat = model.start_chat()
response = chat.send_message(
"Send an email to john@example.com with the subject 'Hello' and body 'Hello from Composio!'"
)
# Execute the function calls the model requested
results = composio.provider.handle_response(session=session, response=response)
print(results)
To execute a single call instead of the whole response, use composio.provider.execute_tool_call(session=session, function_call=part.function_call). For tools fetched with composio.tools.get(), pass user_id= instead of session=.
composio-google vs composio-gemini
This package targets the Vertex AI SDK (vertexai.generative_models, installed via google-cloud-aiplatform). composio-gemini targets the newer google-genai SDK with Automatic Function Calling. For new projects, use composio-gemini.
Links
- Google provider docs: https://docs.composio.dev/docs/providers/google
- Composio docs: https://docs.composio.dev
Metadata
Release files for composio-google 0.29.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| composio_google-0.29.0.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| composio_google-0.29.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.6 kB
Release files / composio_google-0.29.0.tar.gz
| Download URL | composio_google-0.29.0.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2e1f949ad2b13833eada062311d85189498ab9297980f19da3d495a0b2bff7a
|
|
BLAKE2b-256 checksum How to use checksums |
85d928eaecc15ce24d794be92da5d8f553783eb596f5fe6c59feb43543659117
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / composio_google-0.29.0-py3-none-any.whl
| Download URL | composio_google-0.29.0-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93d7795ab9c44f193ad80c53f2fbf8d47f3129886c841b3899165719849b0484
|
|
BLAKE2b-256 checksum How to use checksums |
9a31cecc39a8261cac98d7a85c234487047081e0918ddc396d08f6bd318a8208
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for composio-google 0.29.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
