Accounting · via Zapier

Connect Zunoform to QuickBooks 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 QuickBooks 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 customer or an invoice in QuickBooks from a response, which suits quote requests and service bookings where billing follows the form.

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

Prepare billing details for review before invoicing

A new-client intake can collect the billing name, email and requested service. Start with a customer record or a draft billing workflow. A requested budget is not an approved invoice amount, and a submitted form is not evidence that an invoice was paid.

Prepare your QuickBooks account

Select the correct QuickBooks company and define customer matching. If adding invoices later, use your approved items, tax settings and currency rather than mapping unreviewed free text into financial fields.

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 QuickBooks

Add an action step and choose QuickBooks. Connect your account, then pick the action that creates a customer, an invoice, or a sales receipt. 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.

Billing name and email: Destination: Customer details; Keep billing contact information separate from the project contact when necessary.
Existing customer reference: Destination: Lookup step where supported; Reuse the customer before creating a new one.
Requested service: Destination: Review notes; Translate it to an approved item only after checking the scope.
Response ID: Destination: Supported reference field; Use it to reconcile the intake with the resulting billing record.

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

Test a known customer and a new customer. If your workflow creates a draft invoice, inspect totals, currency and tax treatment before any send action is enabled.

If the result is missing or wrong

Do not replay a multi-step billing Zap without checking which records already exist. A successful customer creation followed by a failed invoice step can otherwise leave duplicate customers or invoices.

Check the current QuickBooks 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 the invoice amount come from the form?

Treat invoice amounts as a separate mapping and approval decision. A budget answer is not a verified payment, and a payment reference is not an invoice line item. Inspect the actual payload and reconcile any payment with your provider before using it in a billing workflow.

Should the invoice be created automatically?

Consider a Zapier filter first. Sending an invoice to every submission including test entries and spam is a mess to unwind in accounting software. Filter on a status answer, or create a draft rather than sending.

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.