> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/google-vertex-ai.md).

# Google Vertex AI

Connect to Google Vertex AI for machine learning and AI services.

This catalog entry does not define workflow actions, event triggers, or knowledge retrieval capabilities.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector                               | Authentication |
| --------------------------------------- | -------------- |
| Google Vertex AI                        | Credentials    |
| Google Vertex AI (Service Account JSON) | Credentials    |

#### Google Vertex AI

Connect to Google Vertex AI to access Google's language models with enterprise-grade security.

**Set up in Google Vertex AI**

1. Make sure you have a Google Cloud project with the Vertex AI API enabled (in the Google Cloud console, go to APIs & Services and enable "Vertex AI API").
2. Confirm your Google account has permission to use Vertex AI in that project (for example the Vertex AI User role).

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Google Vertex AI**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field         | Required | What to enter                                                 |
| --------------------- | -------- | ------------------------------------------------------------- |
| Project ID            | Yes      | Your Google Cloud project ID.                                 |
| Project Location      | Yes      | The location of your Vertex AI resources (e.g., us-central1). |
| Service Account Email | Yes      | The email address of your service account.                    |
| Private Key ID        | Yes      | The private key ID from your service account.                 |
| Private Key           | Yes      | The private key from your service account.                    |

**Provider documentation:** [Setup reference](https://cloud.google.com/vertex-ai/docs).

#### Google Vertex AI (Service Account JSON)

Connect to Google Vertex AI using a service account JSON key file.

**Set up in Google Vertex AI**

1. In Google Cloud, choose the project and enable the API needed by your workflow.
2. Create or select a service account and grant it the required roles.
3. Create a JSON key for the service account. Use the downloaded JSON document in the StackAI credential field.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Google Vertex AI (Service Account JSON)**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field        | Required | What to enter                                                 |
| -------------------- | -------- | ------------------------------------------------------------- |
| Project ID           | Yes      | Your Google Cloud project ID.                                 |
| Project Location     | Yes      | The location of your Vertex AI resources (e.g., us-central1). |
| Service Account JSON | Yes      | The full JSON key file content for your service account.      |

**Connection notes**

* A service-account JSON key contains a private key and account metadata. Paste the full JSON document, not only its private\_key value.

**Provider documentation:** [Setup reference 1](https://cloud.google.com/iam/docs/creating-managing-service-account-keys), [Setup reference 2](https://cloud.google.com/iam/docs/keys-create-delete).

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Important behavior

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/google-vertex-ai.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
