Email marketing · via Zapier

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

Creates or updates a Brevo contact from each response and adds them to the list you choose, with answers stored as contact attributes.

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

Collect event interests without mixing up contact attributes

An event interest form can capture a preferred city, topic and email address for later announcements. Store preferences as attributes so your team can choose relevant audiences, and distinguish interest from a confirmed event registration.

Prepare your Brevo account

Create the intended Brevo attributes and check their types. Choose a list for people who opt in, and decide whether Brevo or Zunoform will send any acknowledgement so respondents do not receive duplicate messages.

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 Brevo

Add an action step and choose Brevo. Connect your account, then pick the action that creates or updates a contact and adds it to a list. 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: Contact identity; Test update behavior with an existing address.
Preferred city: Destination: Text attribute; Keep city choices consistent with your segmentation rules.
Event topic: Destination: Configured attribute; Confirm how multiple preferences should be represented.
Announcement opt-in: Destination: Filter before list addition; An enquiry alone should not silently become a subscription.

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 Brevo 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 a full response and one with optional preferences blank. Inspect attributes on the contact and confirm only the intended acknowledgement is sent.

If the result is missing or wrong

Missing values often point to an attribute-name or type mismatch. Refresh the action after adding attributes, and avoid overwriting existing preferences with empty answers.

Check the current Brevo 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

Do Brevo attributes need to exist first?

Yes. Create the attributes in Brevo before you build the Zap, then refresh the action fields and confirm the values reach the contact in a test.

Can Brevo send the confirmation email instead of Zunoform?

It can, and sometimes should. Zunoform supports form notifications using your own SMTP configuration on Free, and platform-sent form emails on Pro and Business, but if you want the confirmation to match your marketing templates, let Brevo send it from an automation triggered by the new contact.

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.