The repository or configuration that created this release differ from a previous release. View details.
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.32.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| composio_google-0.32.0.tar.gz | 4.2 kB | With provenance | Details for composio_google-0.32.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| composio_google-0.32.0-py3-none-any.whl | Python 3 | none | any | Details for composio_google-0.32.0-py3-none-any.whl |
Total release size: 8.6 kB
Release files / composio_google-0.32.0.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | composio_google-0.32.0.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53a13e91e0ab31f974c779386be3a955345e46be070348df076686bb640f012f
|
|
BLAKE2b-256 checksum How to use checksums |
d1fa3dbf1cb2348aa377b647b92ad07040b7873fad8e52e04b4656b9c74d69ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logRelease files / composio_google-0.32.0-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | composio_google-0.32.0-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21d31103d336b53c3cc383b8a19f3bf4d9b6875b512ff59b36734446b416769a
|
|
BLAKE2b-256 checksum How to use checksums |
5f82ac0afb03171c0694b6d7173beabc7208079d4ce1363d9badc22b0258dbd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logSecurity for composio-google 0.32.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.
Change of provenance
The configuration that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Attestation for composio_google-0.32.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.