Google Forms
Google Forms response automation
Google Forms gets a deceptively narrow API surface — Tiny Command exposes one trigger (Response Submitted — fires when someone submits a form response) plus four actions (List Forms, Get Form returning the question schema, Get Response, Get Responses paginated history). The connection uses Google OAuth with the forms.readonly or forms.body scope; the user picks a form at trigger setup. Response Submitted is the workflow trigger for every form-to-anywhere pattern: lead form → CRM contact, support form → ticket system, RSVP form → calendar event. The payload includes the responseId, the submission timestamp, the respondent email (when the form requires sign-in), and the answers array keyed by question ID. Crucially, the answer values are strings (or arrays of strings for multi-select) — Google doesn't type the answers by question type at the API level, so a checkbox answer is `["Yes", "Maybe"]` and a date answer is `"2026-06-15"`. The question ID-to-text mapping comes from Get Form, which workflows typically cache and join in a downstream Map step.
Workflows start when Google Forms does.
1 real-time trigger, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Do anything Google Forms can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Get Google Form | Returns the form definition with questions, IDs, and labels. The lookup for resolving question IDs to readable labels in downstream notifications — Google Forms uses opaque question IDs in submissions. |
| Get Form Response | Returns a specific response by ID with all answers. Useful for re-fetching responses captured via webhook with richer detail. |
| List Form Responses | Paginated responses for a specific form. Useful for backfill workflows that catch responses missed during webhook downtime or for periodic batch-processing of all responses. |
| List Google Forms | Returns forms the connected account can see. Useful for resolving form IDs at workflow setup or for inventorying form catalog. |
Pre-built Google Forms workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Google Forms event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Google Forms into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Google Forms once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Google Forms field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Google Forms integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Google Forms to Tiny Command?
What Google Forms triggers does Tiny Command support?
What Google Forms actions can I run from a workflow?
Is the Google Forms integration real-time?
Do I need to write code to use Google Forms with Tiny Command?
How much does the Google Forms integration cost?
More forms & surveys apps people connect.
Same category as Google Forms, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Google Forms.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
