Generate image · Google

Node catalog Actions

On this page

Create or transform an image with Google.

Usage and specifics

Choose an accessible model and prompt. Image references and JSON parameters depend on the model. For asynchronous generation, retrieve its jobId with the status operation and the same credentials. Stopping locally does not guarantee stopping provider work or billing. Completed output contains data, encoding and mimeType.

Technical type : generate_image_google. Runtime : nodulz.

Credentials and prerequisites

Create and configure the credential : gemini

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialId`	`string`	`""`	-
`operation`	`enum`	`"generate"`	`generate`, `status`
`model`	`string`	`"gemini-3.1-flash-image"`	-; min 1
`prompt`	`string`	`""`	-
`inputImage`	`string`	`""`	-
`jobId`	`string`	`""`	-
`waitForCompletion`	`boolean`	`true`	-
`timeoutSeconds`	`number`	`600`	-; ≥ 1, ≤ 3600
`parameters`	`string`	`"{}"`	-

Configuration help

credentialId AI credential: API credential for the selected provider. The key stays encrypted on the server.
operation Operation: Generate creates a new job. Retrieve checks an existing job without starting another generation.
waitForCompletion Wait for result: Disable to return a jobId immediately, then retrieve the generation after a pause. The global workflow timeout also applies.
timeoutSeconds Timeout (seconds): Local limit from 1 to 3600 seconds. For long jobs, also adjust server WORKFLOW_RUN_TIMEOUT_MS. Stopping locally does not guarantee cancellation of provider billing.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "operation": "generate",
  "model": "gemini-3.1-flash-image",
  "prompt": "",
  "inputImage": "",
  "jobId": "",
  "waitForCompletion": true,
  "timeoutSeconds": 600,
  "parameters": "{}"
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.