Short answer: Drop the "Google Forms → Google Forms Response Submitted" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Google Forms, not on a polling schedule.
Drop it on the canvas. Configure a couple of fields. Publish.
You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"answers": {"1e2f3g4h": {"questionId": "1e2f3g4h","textAnswers": {"answers": [{"value": "5"}]}}},"createTime": "2026-04-20T14:30:00Z","responseId": "ACYDBNh1abc123","respondentEmail": "respondent@example.com"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| answers | object | { … } |
| answers.1e2f3g4h | object | { … } |
| answers.1e2f3g4h.questionId | string | "1e2f3g4h" |
| answers.1e2f3g4h.textAnswers | object | { … } |
| answers.1e2f3g4h.textAnswers.answers | array | [{"value":"5"}] |
| createTime | string | "2026-04-20T14:30:00Z" |
| responseId | string | "ACYDBNh1abc123" |
| respondentEmail | string | "respondent@example.com" |
One trigger. 4+ downstream actions. Zero glue.