Email marketing · via Zapier

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

Subscribes respondents to a Klaviyo list and writes their answers onto the profile as properties you can segment on later.

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

Build a preference-led product waitlist

A product waitlist can collect an email and a preference such as product category or intended use. Those answers help you send a relevant launch message, but joining a waitlist does not reserve stock or create an order.

Prepare your Klaviyo account

Choose the list and review its subscription settings. Keep profile creation, list membership and marketing consent distinct in your Zap; an action that updates a profile is not necessarily a subscription action.

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 Klaviyo

Add an action step and choose Klaviyo. Connect your account, then pick the action that subscribes a profile to a list, or updates a profile. 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.

Email: Destination: Profile identity; Use an address you own for the first test.
Product preference: Destination: Profile property; Use consistent option values so later segments are easy to define.
Opt-in answer: Destination: Filter before subscription; Do not subscribe someone solely because an email field was completed.
Fixed launch name: Destination: Source property; Separate this waitlist from your general newsletter.

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 Klaviyo 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 new subscriber and an existing profile, including the confirmation journey if enabled. Inspect both list membership and the preference property used by your segment.

If the result is missing or wrong

If the profile exists but is absent from the list or segment, check subscription status, confirmation requirements and the exact property value. Do not bypass suppression settings to make a test appear successful.

Check the current Klaviyo 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 segment on answers from the form?

Yes, that is the main reason to do this. Map each answer to a profile property and Klaviyo segments on it like any other property — a preference question becomes a segment without any extra work.

Does this work for a pre-launch waitlist?

It is a common use of it. A conversational Zunoform waitlist form on the free plan, a Zap into Klaviyo, and your flows do the rest. The free plan's 500 responses a month is the ceiling to watch.

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.