Customer support · via Zapier

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

Opens a Zendesk ticket for every submission, which lets a support-request form on your own site feed the queue agents already watch.

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

Create support tickets with the right requester

A support form can collect the reply address, affected product, description and order reference before opening a ticket. Keep the public form short while making the first ticket comment useful enough for an agent to begin investigating.

Prepare your Zendesk account

Choose the destination brand or group where your Zendesk action supports it. Decide whether the initial comment should be public or internal, and check the requester mapping before using real customer addresses.

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 Zendesk

Add an action step and choose Zendesk. Connect your account, then pick the action that creates a ticket. 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.

Customer email: Destination: Requester identity; Replies should reach the customer, not the account that authorized Zapier.
Issue summary: Destination: Ticket subject; Use the product or order context to distinguish similar requests.
Description and order reference: Destination: Initial comment; Label the reference; it is not proof of an order by itself.
Issue category: Destination: Tag or configured field; Translate categories to your support team's accepted values.

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

Create a ticket using an address you control and send a test reply. Check its recipient, comment visibility and group assignment before enabling notifications for customers.

If the result is missing or wrong

If ticket creation succeeds but replies go to the wrong person, fix the requester mapping. File references in a comment are not native attachments; test access or add a supported upload step.

Check the current Zendesk 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 set the requester so replies reach the right person?

Yes, and you should. Map the email answer to the ticket's requester field, otherwise the ticket is created as the account that authorized the Zap and replies go nowhere useful.

How do uploaded files reach the ticket?

Zunoform sends file uploads as URLs. Put the URL in the ticket comment so an agent can open it, or add a step that downloads and re-uploads the file if you need a true attachment.

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.