Run a Gemini Live voice support assistant with Google Drive and Sheets

## Untitled workflow ### How it works The workflow powers a voice assistant backend with two webhook entry points: one to issue a Gemini live-session token and another to handle tool calls from the voice session. Token requests are rate-limited, enriched with knowledge files from Google Drive, signed, and exchanged for an ephemeral Gemini token before returning session details to the client. Tool calls are signature-validated, routed to order status, return creation, complaint logging, owner notification, or invalid-request handlers, then returned through a shared webhook response. ### Setup steps - Configure both webhook URLs for the client voice app: one for session/token requests and one for tool-call callbacks. - Add Google Drive credentials and set the knowledge folder or file source used by the knowledge-loading nodes. - Add Google Sheets credentials and configure the order, return request, and complaint sheets/ranges used by the Sheets nodes. - Add Gmail credentials for owner notification emails and set the owner/support email values in the business settings node. - Configure the Gemini API key or HTTP authentication for the ephemeral token request, plus any signing secret used by the crypto nodes. - Review the code nodes for expected request payload fields, signature headers, rate-limit storage assumptions, and response schemas. ### Customization Update the business settings, supported knowledge file types, rate-limit thresholds, Gemini live-session configuration, tool routing cases, sheet column mappings, and email templates to match the business process.