Ecommerce · via Zapier

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

Creates a Shopify customer from each response, which turns wholesale applications, pre-order interest forms, and product questionnaires into records in your store.

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.

This creates records in Shopify; it does not take the money. If you want to charge someone inside the form, Zunoform's payment field runs on your own Stripe or PayPal keys with no platform cut, on the $14.99 plan, and does not involve Zapier at all.

Example workflow

Collect wholesale interest for store-owner review

A wholesale application can collect company, contact details and intended order size before creating or updating a Shopify customer. This is an intake record, not approval for wholesale pricing and not a paid order.

Prepare your Shopify account

Check the connected store and the customer action's permissions. Decide how to handle an existing email and choose a review tag your team understands. Keep marketing subscription separate from the application itself.

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 Shopify

Add an action step and choose Shopify. Connect your account, then pick the action that creates a customer, or another record your store supports. 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.

Contact email and name: Destination: Customer identity; Use lookup/update behavior when appropriate for existing customers.
Company and application details: Destination: Supported note or customer fields; Store only information your review team needs.
Fixed wholesale-review tag: Destination: Customer tag; A review tag should not automatically grant a discount.
Marketing preference: Destination: Separate consent handling; Do not infer a marketing subscription from a wholesale enquiry.

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 Shopify 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 a new applicant and an existing store customer's email. Check tags and preserved details, then confirm no order, discount entitlement or marketing subscription was created unintentionally.

If the result is missing or wrong

If the customer action rejects an email already in the store, add the appropriate lookup/update path. Do not create variations of the email to force duplicates past validation.

Check the current Shopify 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 this create an order?

What Zapier's Shopify connection lets you create depends on the actions it currently offers and on your store's permissions. Customers are the reliable case. For anything transactional, take the payment in the form with a Zunoform payment field and let the Zap record the rest.

Can I tag customers by their answers?

Yes. Map an answer to the customer tags field, or set fixed tags in the Zap so every submission from a given form is identifiable later in Shopify.

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.