Short answer: Drop the "Google Forms → Get Form Response" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Form ID form_id | string | Required | The unique identifier of the Google Form |
Response ID response_id | string | Required | The unique identifier of the form response |
{"form_id": "e.g. 1BxiMVs0XRA5nFMdj5n76UEAf3RCmWMR6","response_id": "e.g. ACYDBNh1abc123"}
{"answers": {"1e2f3g4h": {"questionId": "1e2f3g4h","textAnswers": {"answers": [{"value": "5"}]}},"5a6b7c8d": {"questionId": "5a6b7c8d","textAnswers": {"answers": [{"value": "Great service, very responsive team!"}]}}},"createTime": "2026-04-20T14:30:00Z","responseId": "ACYDBNh1abc123","respondentEmail": "respondent@example.com","lastSubmittedTime": "2026-04-20T14:32:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.