Skip to main content

Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Google Gemini connector page.

How webhook setup works

StackOne creates and manages the Google Gemini webhook subscription automatically when the account is connected, and removes it when the account is disconnected. There is no URL to copy and nothing to configure in Google.

1

Enable the events you want

In the StackOne dashboard, open the Google Gemini connector profile and enable the webhook events you want delivered. StackOne registers a single project-level subscription covering exactly those events. Changing the selection re-registers the subscription.

2

Review what the subscription covers

A Google Gemini webhook is scoped to the Google Cloud project behind the connected credential, so one linked account maps to one subscription. Events are generated by asynchronous work in that project — batch jobs, background interactions, and Veo video generation. Accounts that only make synchronous requests will never receive an event.

  • The subscription is created with the same API key or OAuth credential used by the rest of the connector. No extra permissions are needed.
  • Google signs each delivery with its own signing secret, issued when the subscription is created.

Available webhook events

The following Google Gemini events can be enabled. Only events selected in StackOne are included in the subscription — Google will not deliver events that are not subscribed.

1

Enable batch events

Events related to the lifecycle of asynchronous batch jobs.

  • Batch Succeeded (batch.succeeded) — Fired when a batch job finishes processing successfully and its results file is ready
  • Batch Failed (batch.failed) — Fired when a batch job terminates with a system or validation error
  • Batch Expired (batch.expired) — Fired when a batch job is not processed within its 24-hour window and is discarded
2

Enable interaction events

Events related to long-running interactions submitted with background processing.

  • Interaction Completed (interaction.completed) — Fired when a background interaction finishes successfully
  • Interaction Failed (interaction.failed) — Fired when a background interaction terminates with an error
  • Interaction Requires Action (interaction.requires_action) — Fired when an interaction pauses and waits for a function call result to be supplied
3

Enable video events

Events related to Veo video generation.

  • Video Generated (video.generated) — Fired when a Veo video generation job finishes and the output file is ready to download

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.