Short answer: Drop the "Google Gemini → Gemini Generate Content" 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 | Required | Which Gemini model to use |
Prompt prompt | string | Required | Your prompt |
System Instruction system_instruction | string | Optional | System-level guidance |
Temperature temperature | string | Optional | 0–2 |
Max Output Tokens max_output_tokens | string | Optional | 2048 |
Top P top_p | string | Optional | 0.95 |
Top K top_k | string | Optional | 40 |
{"model": "{{trigger.model}}","prompt": "{{trigger.prompt}}","system_instruction": "{{trigger.system_instruction}}","temperature": "0.7","max_output_tokens": "2048"}
{"candidates": [{"content": {"role": "model","parts": [{"text": "Sample response"}]},"finishReason": "STOP"}],"usageMetadata": {"totalTokenCount": 60,"promptTokenCount": 10,"candidatesTokenCount": 50}}
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.