Files · via Zapier

Connect Zunoform to Dropbox 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 Dropbox 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.

Saves files uploaded through your form into a Dropbox folder, which suits application and submission forms where the attachment is the point.

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.

Example workflow

Collect project assets without filename collisions

A project intake form can gather a logo, reference document or photograph for a delivery team. Use a predictable folder and filename convention so a second client uploading logo.png does not become indistinguishable from the first.

Prepare your Dropbox account

Choose a Dropbox destination accessible to the connected account. Decide whether to keep all files in an intake folder or create one folder per response. Check the action's overwrite behavior before using real assets.

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 Dropbox

Add an action step and choose Dropbox. 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.

Upload URL from the test response: Destination: File input; Verify that Zapier can fetch the original file.
Response ID plus original filename: Destination: File name or path; A unique response reference is safer than a customer name alone.
Fixed intake folder: Destination: Destination path; Keep path formatting consistent and inspect any generated subfolders.

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

Submit two different files with the same original filename. Open both saved copies and confirm that your naming rule preserves them rather than replacing one.

If the result is missing or wrong

A single upload action may not process every item in a multi-file answer. Inspect the sample structure and use supported iteration for multiple files; do not pass a comma-separated list as though it were one downloadable URL.

Check the current Dropbox 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 are the files named?

However you map it. The default is the original filename, which collides when two people upload resume.pdf. Prefix it with an answer — surname, company, submission time — to keep them distinct.

Is there a file size limit?

Two of them: Zunoform's upload limit on your plan, and whatever Zapier allows a step to transfer. The Zunoform limit applies first, since the file has to be accepted before there is anything to send.

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.