Files · via Zapier

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 connection with field mapping you control in Zapier.

Copies files uploaded through your form into a Google Drive folder, and can create a folder per response so submissions stay separated.

Start free — no card See native integrations

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.

Zunoform sends file uploads as URLs in the response payload, not as binary attachments. The upload step must be able to fetch the file from the reference you map. Test access, file contents and transfer limits with your own configuration before relying on the workflow.

Example workflow

Organize application files in a dedicated Drive folder

An application form can collect a portfolio or supporting document and place a copy in a review folder. Keep the response data and file storage roles separate: a spreadsheet tracks status, while Drive holds the actual documents.

Prepare your Google Drive account

Select a destination folder the connected account can write to. Inspect a real upload in the webhook sample to find its file reference. Confirm that the URL supplies file bytes to Zapier rather than an authenticated preview page.

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 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.

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.

Uploaded file reference: Destination: File input; Select one usable file URL; a multi-file answer may require iteration.
Response ID and filename: Destination: Destination filename; Use a stable prefix so two portfolio.pdf uploads remain distinguishable.
Fixed review folder: Destination: Parent folder; If creating a folder first, pass its returned identifier to the upload step.

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 Drive 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

Upload a small document, then download the resulting Drive file and open it. Test two files and repeated filenames if the form permits them; a successful action is not enough if the saved file is a preview page.

If the result is missing or wrong

If the file is empty or inaccessible, check the source URL's access requirements and the transfer limits of each service. Do not make an entire storage bucket public to solve one mapping problem.

Check the current Google Drive 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

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. 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.