Short answer: Drop the "Google Vertex AI → Imagen Generate" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Model model | options | Optional | Model. Options: Imagen 4, Imagen 3 Fast |
Prompt prompt | string | Required | Prompt (required) |
Number of Images sample_count | string | Optional | Number of Images |
Aspect Ratio aspect_ratio | options | Optional | Aspect Ratio. Options: 1:1, 16:9, 9:16 … |
{"model": "{{trigger.model}}","prompt": "{{trigger.prompt}}","sample_count": "{{trigger.sample_count}}","aspect_ratio": "{{trigger.aspect_ratio}}"}
{"predictions": [{"mimeType": "image/png","bytesBase64Encoded": "<base64>"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.