Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ AI ]

Google Vertex AI integration for your workflows.

Connect Google Vertex AI to Collabase once and use 3 actions in your workflows. No code needed, hosted in Switzerland.

Sign-inCustom credentials
CategoryAI
UpdatedOctober 2026
LicenceOpen source (MIT)
Back to the directory

Google Vertex AI in Collabase

Connect Google Vertex AI to Collabase once and use 3 actions in your workflows. No code needed, hosted in Switzerland.

[ About the service ]

Generate content and images using Gemini and Imagen models on Google Vertex AI.

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Google Vertex AI and connect your account.
  3. Add a trigger or an action to the workflow.
  • Go to Google Cloud Console.
  • Create a new project or select an existing one.
  • Enable the Vertex AI API under APIs & Services > Enabled APIs.
  • Create a Service Account:
  • Go to IAM & Admin > Service Accounts.
  • Click Create Service Account, fill in the details and click Create.

[ AI ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Google Vertex AI

What can I automate with Google Vertex AI in Collabase?

Google Vertex AI brings 3 actions and 0 triggers, for example Generate Content, Generate Image and Custom API Call. You combine them in a workflow without code and mix them with every other integration.

How do I connect Google Vertex AI to Collabase?

You open the integrations in the workspace settings, choose Google Vertex AI and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.

Does the Google Vertex AI integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.