Ecommerce · via Zapier

Connect Zunoform to WooCommerce 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 WooCommerce 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 WooCommerce customer record from each response, so a form hosted outside WordPress still populates the store you run inside it.

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

Capture trade-account enquiries outside WordPress

A separate form can collect a business profile and contact details for a WooCommerce store. Decide whether you want an actual customer account or simply an enquiry for review; account creation can have consequences such as welcome emails.

Prepare your WooCommerce account

Check the current WooCommerce connector's plugin, authentication and permission requirements before building the Zap. Confirm the store is reachable and that your chosen action has only the access it needs.

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 WooCommerce

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

Email and name: Destination: Customer fields; Test with an existing customer as well as a new address.
Business name: Destination: Supported company field; Do not invent billing information that the applicant did not provide.
Application context: Destination: Supported notes or separate review record; Use a review destination if the customer action cannot store the details.

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

Use a test store or an address you own. Confirm whether an account and any emails are created, and check that application submission does not place an order or grant a trade discount.

If the result is missing or wrong

If authentication fails, check the connector's current setup requirements and your store's firewall or maintenance settings. Generic REST API access alone may not satisfy the selected Zapier connector.

Check the current WooCommerce 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

What does the WooCommerce connection need on my site?

Check the current WooCommerce connector for its plugin, authentication and permission requirements. Your store must be reachable by Zapier; maintenance mode or firewall rules can prevent connection even when credentials are correct.

Can I use this for a paid order form?

You can take the payment in Zunoform instead. Our payment field uses your own Stripe or PayPal keys, and per-option amounts can be driven by an earlier question, with totals recomputed on the server at checkout and re-verified at submission.

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.