Connect Zunoform to Google Drive 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 Drive button inside Zunoform and no OAuth connection between the two products. What you get instead is a webhook and about five minutes of setup.
Copies files uploaded through your form into a Google Drive folder, and can create a folder per response so submissions stay separated.
The Zapier integration is on Zunoform’s free plan — 500 responses a month, no card. Your own Zapier plan and its task limits still apply, and they are billed by Zapier, not by us.
Zunoform sends file uploads as URLs in the response payload, not as binary attachments. Zapier's Drive action fetches the file from that URL, which works, but it is a fetch rather than a direct handoff — very large files are the case to test first.
Four steps, start to finish
You need a Zunoform form and a Zapier account. Nothing is installed on either side.
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 Drive
Add an action step and choose Google Drive. Connect your account, then pick the action that uploads a file or creates a folder. 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.
What Zapier receives
One payload per completed response, containing the form’s questions and the answers given, delivered from a queue with retries rather than dropped on a failure. Multi-part answers arrive as their component parts, and file uploads arrive as URLs rather than binary attachments — worth knowing before you build a step that expects a file. Responses collected before you connected the hook are not replayed; delivery starts from the moment the integration is on.
Questions people ask
Can I create one folder per submission?
Yes. Add a create-folder action named from an answer — a company name, an application ID — then upload the files into the folder ID that step returns.
What about the response data itself, not the files?
Use our native Google Sheets integration for that. It is on the free plan, it writes one row per response with multi-part answers split into their own columns, and it needs no Zapier account.
Is this a native Zunoform integration?
No, and we would rather say so on the page than in a support ticket. Zunoform posts each completed response to a Zapier catch hook, and Zapier does the rest. There is no OAuth connection between the two products and no per-field configuration inside Zunoform. Our native integrations — the ones with a Connect button — are Google Sheets, Zoho CRM, Google Calendar, Outlook Calendar, webhooks, email, and reCAPTCHA on the free plan, plus Slack, Notion, HubSpot, Mailchimp, Airtable, and Excel on Pro.
Also in Files
Better forms.
Better data.
Build your first form in under 60 seconds. Free forever for personal use, no credit card required.