Connect Zunoform to Google Docs via Zapier
This is not a one-click native integration. Zunoform posts every completed response to a Zapier catch hook, and your Zap does the rest — so there is no Google Docs button inside Zunoform and no OAuth connection between the two products. What you get instead is a webhook connection with field mapping you control in Zapier.
Generates a Google Doc from a template for each response, filling placeholders with the answers — useful for briefs, intake summaries, and simple agreements.
The Zapier integration is on Zunoform’s free plan — 500 responses a month, no card. Webhooks by Zapier requires a paid Zapier plan; destination account requirements and task limits also apply.
Example workflow
Generate an editable client brief from answers
A project intake can become a Google Doc with sections for goals, audience, scope and open questions. Use it as a draft for a discovery meeting, not as a signed agreement or automatically accepted statement of work.
Prepare your Google Docs account
Create a template document the connected account can access. Add the placeholder markers supported by the current Zapier action and keep a separate original so test runs do not overwrite your working template.
Four steps, start to finish
Start with a published Zunoform form, a Zapier plan that includes webhooks, and access to the destination account. Some destinations require additional permissions or setup.
Create a Zap with a Catch Hook trigger
In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger app, then Catch Hook as the event. Zapier generates a URL for you and shows it on the next screen. Copy it.
Paste the URL on the Zapier card in Zunoform
Open your form in the Zunoform builder, go to the Integrations tab, and paste the URL on the Zapier card. We only accept an https address on zapier.com, so a typo is rejected rather than silently failing later.
Submit a test response so Zapier learns the shape
Publish the form and fill it in once yourself. Zapier's trigger step will pick that submission up as sample data — without it, the field list in the next step is empty and there is nothing to map.
Map your fields to Google Docs
Add an action step and choose Google Docs. Connect your account, then pick the action that creates a document from a template. Zapier's action list changes over time, so choose from what it shows you rather than hunting for an exact name. Drag your form's answers into the fields, test the Zap, and turn it on.
Suggested field mapping
Use this example to plan your form. Select the actual fields from your captured test response and the action available in your account; these are mapping suggestions, not a preconfigured Zap.
- Project name
- Destination: New document title
- Include the response ID or date to distinguish revisions.
- Audience and goals
- Destination: Matching template placeholders
- Use separate markers so the brief retains its structure.
- Scope and working budget
- Destination: Brief sections
- Label the budget as an estimate supplied by the respondent.
- Optional notes
- Destination: Notes placeholder
- Decide what the document should show when this answer is blank.
What Zapier receives
The payload includes formId, formName, responseId, submittedAt, status, answers and metadata. Answers are keyed by field ID, not by question label; inspect a test response to identify the answer you want. Multi-part answers can contain nested values, and uploads contain file references rather than binary attachments. Replacing a question can change its ID, so retest mappings after editing the form.
Delivery uses a background queue with retries for failed webhook requests. A successful hook does not confirm the later Google Docs action succeeded. Check Zap history, and use responseId in a lookup or a processed-response log when duplicate processing would matter. Earlier responses are not automatically replayed when you connect the hook.
Test before sharing your form
Generate a document with long answers and another with optional fields empty. Read the resulting documents for unreplaced markers, layout problems and accidental changes to the original template.
If the result is missing or wrong
If markers remain visible, compare their exact spelling with the action's fields and refresh the template mapping. File or signature references require separate handling; they do not automatically become embedded images or verified signatures.
Check the current Google Docs actions in Zapier and Zapier’s webhook setup and plan requirements before configuring your account. Action availability and permissions depend on your connected account.
Questions people ask
How do the placeholders work?
Write your template with markers where the answers go, then map each form answer to the matching marker in the Zap. Zapier's template action replaces them when it creates the copy.
Can this produce a signed document?
Not on its own. Zunoform has an e-signature question type on the Pro plan that captures a signature inside the form, and the signature comes through in the response. Turning that into a countersigned PDF needs a document tool further down the Zap.
Is this a native Zunoform integration?
No. Zunoform sends each completed response to your Zapier catch hook; you configure the destination and field mapping in Zapier. The Zunoform connection is included on Free, but Webhooks by Zapier requires a paid Zapier plan. Native options include Google Sheets and Zoho CRM on Free, with Slack, Notion, HubSpot, Mailchimp, Airtable and Excel on Pro. Form notification emails on Free require your own SMTP configuration; platform-sent form emails require Pro or Business.
Ready when you are
Better forms.
Better data.
Start with a conversation, a document or a single page.
Unlimited forms and 500 responses per month on Free.
No card required.
- No credit card
- Unlimited forms
- 500 responses / month