Customer support · via Zapier

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

Starts a Help Scout conversation from each response, so a contact form on your site arrives in the shared inbox rather than in one person's email.

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

Bring partnership enquiries into a shared mailbox

A partnership form can collect organization, proposal and reply details, then start a Help Scout conversation for the team that evaluates offers. Use a dedicated mailbox when partnerships have different owners or response expectations from customer support.

Prepare your Help Scout account

Select the mailbox and decide how new conversations should be assigned. Confirm which fields identify the customer and which create the conversation body in the action you choose.

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 Help Scout

Add an action step and choose Help Scout. Connect your account, then pick the action that creates a conversation in a mailbox. 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: Customer identity; Use the submitter's address so a response reaches the right person.
Organization and proposal title: Destination: Subject; Make it recognizable in the shared inbox.
Proposal and timing: Destination: Conversation body; Include the original details instead of a generic New form response message.
Fixed partnership mailbox: Destination: Mailbox; Keep the destination controlled by the team.

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 Help Scout 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

Send a test enquiry and reply from Help Scout to an address you own. Confirm mailbox placement and that the conversation is associated with the intended customer.

If the result is missing or wrong

If messages arrive in a personal or unexpected inbox, review the mailbox selection and authorization. A successful hook only confirms Zapier received the form response, not that mailbox routing is correct.

Check the current Help Scout 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

Which mailbox does the conversation land in?

Whichever you pick in the Zap. Teams running several forms usually point each one at a different mailbox — sales enquiries to one, support to another — which is configured per Zap, not per Zunoform form.

Can the customer reply to the conversation?

Yes, provided you map their email address to the customer field on the action. Help Scout then treats the thread as a normal conversation with that person.

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.