Important form response logged and escalated to an existing Chat space

Every Form response is logged once, while only responses matching the exact high-priority rule create an escalation post in the existing Chat space.

Starter: When a form response comes in (an operational intake Google Form with a priority field)

1. Log every responseSheetsUse Sheets 'Add a row' to record the submission, requester, priority, owner, and source link before any escalation decision.
2. Check the priority ruleUse 'Check if' to continue the escalation substeps only when the submitted priority equals your exact high-priority value. Keep the rule deterministic rather than asking Gemini to infer urgency.
3. Post the escalation to ChatChatInside the condition, use Chat 'Post in a space' to post the minimum actionable summary, Sheet link, and named owner to an existing operations space.

• Requester — Person or team submitting the Form. (e.g. Finance)
• Priority — A controlled Form value used by Check if. (e.g. High)
• Request summary — The concise operational issue from the Form. (e.g. Payroll file access blocked)
• Owner — The internal person named to take the next action. (e.g. helpdesk@example.com)

Paste this draft into Google Workspace Studio's Describe it with AI box, then review and adjust the flow it builds. This is Google's Gemini feature — CertPilot does not run any AI.

• An eligible Google Workspace edition with Workspace Studio and Gemini enabled by your admin.
• Access to Sheets and Chat (subject to your admin's Studio step controls).
• A Google Form with a controlled priority field, an Intake Log Sheet, and an existing operations Chat space.

Security notes

• Use controlled Form choices for the priority rule; do not allow free text to decide whether the escalation runs.
• Post only the minimum actionable detail to Chat and keep sensitive evidence in the restricted Sheet.
• Subject to your admin's Studio controls, DLP, and external-user approval policy.

What it does not do

• The flow trusts the submitted priority value; it does NOT independently assess severity or validate the request.
• Chat cannot create a space — the escalation posts to an existing one.
• It logs and notifies only; it does not assign a ticket, page an on-call service, or resolve the request.

• Workspace Studio test runs take real actions — this test really adds Sheet rows and posts matching responses to Chat.
• Submit one Low and one High fictional response to a test Form connected to a test Sheet and Chat space.
• Confirm that both rows are logged but only the exact High value produces a Chat post.

Primary source

Last verified 26 August 2026

Related recipes

• Helpdesk request intake (log to a Sheet, notify Chat, acknowledge by email)
• Onboarding readiness handoff between the hiring manager and IT
• Vendor intake register with owner notification and requester receipt

← All Workspace Studio recipesBuild your own flow blueprint