CRM · via Zapier

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

Every completed form response becomes a lead, contact, or record in Salesforce, with your questions mapped to the fields your team already reports on.

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

Turn a demo request into a lead your sales team can qualify

A demo form can collect work email, company, role and the problem someone wants to solve. Start by creating a lead for review rather than treating every submission as a qualified opportunity. The enquiry text gives the salesperson context for the first conversation.

Prepare your Salesforce account

Ask your Salesforce administrator which object, required fields and duplicate rules apply. Use an integration account with permission to create that object. Decide how to handle an email address already present in your CRM before enabling the Zap.

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 Salesforce

Add an action step and choose Salesforce. Connect your account, then pick the action that creates the record type you want — a lead, a contact, or a custom object. 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.

Name and work email: Destination: Lead identity fields; Collect name parts separately if your Salesforce setup requires them.
Company: Destination: Company field; Make this required in a business enquiry form if your lead configuration requires it.
Problem to solve: Destination: Description; Include the response ID so the team can trace the original enquiry.
Fixed value: Website demo: Destination: Lead source; Choose a value allowed by your Salesforce configuration.

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

Submit one new email address and one address already in Salesforce. Confirm the intended create, update or review behavior, then check ownership and lead source in the actual record.

If the result is missing or wrong

If the hook succeeds but no lead appears, inspect the Salesforce action in Zap history. Missing required fields, restricted picklist values and duplicate rules need different fixes; repeatedly resending the same submission will not resolve them.

Check the current Salesforce 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 Salesforce editions work with this?

Zapier's Salesforce connection requires an edition with API access, which rules out some of the lowest Salesforce tiers. Check your edition before building the Zap — the Zunoform side works regardless, but the Zap will not connect without API access.

Can I set the lead source or owner automatically?

Yes, in the Zap rather than in Zunoform. Any field Salesforce exposes on the action can be filled with a fixed value you type into Zapier, so lead source, campaign, and owner can be constants while the rest come from the form.

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.