Customer support · via Zapier

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

Each response becomes a Freshdesk ticket with the form's answers as the description, so intake happens on your form and triage happens in Freshdesk.

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

Route service requests without losing the original explanation

A service request form can distinguish billing, product and account issues before they reach Freshdesk. Use the category for routing while retaining the full explanation, since a short dropdown answer rarely gives an agent enough information to solve a case.

Prepare your Freshdesk account

Agree on the default group and priority for new requests. Check the action's accepted values for required ticket fields and create any custom fields in Freshdesk before mapping them.

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 Freshdesk

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

Reply email: Destination: Requester email; Make it required if the workflow depends on a reply.
Request summary: Destination: Subject; Keep the subject descriptive and place background in the body.
Explanation: Destination: Description; Include the response ID for tracing the original submission.
Category: Destination: Group or custom field; Use explicit mappings; do not treat an arbitrary answer as a group ID.

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 Freshdesk 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 each category and confirm the resulting group. Also test an unanswered optional attachment field so the description does not contain broken or empty links.

If the result is missing or wrong

When a ticket is rejected, inspect status and priority values as well as required contact information. Fix the failed action before replaying it, and check whether an earlier run already created the ticket.

Check the current Freshdesk 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 group or priority automatically?

Yes. Both are fields on Zapier's Freshdesk action. Set them to fixed values, or map a dropdown answer so urgent requests land in the right group without a human sorting them.

Is there a native Freshdesk integration?

No. Freshdesk is one of the tools we reach only through Zapier or a plain webhook. Native options include Google Sheets and Zoho CRM on Free, plus Slack, Notion, HubSpot, Mailchimp, Airtable and Excel on Pro. Free form email notifications require your own SMTP configuration.

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.