Zapier integration

Zapier connects apps with Zaps: a trigger, like a new form submission, and one or more actions. Webflow has a native Zapier integration with a New Form Submission trigger; Framer forms reach Zapier through their webhook destination; on Astro and Next.js we post to a Zapier Catch Hook from a server route. Your team can then change where leads go without a developer.

Updated

Official sources

  1. Webflow integrations (opens in a new tab)Zapier · zapier.com
  2. Common problems with Webflow (opens in a new tab)Zapier Help · help.zapier.com
  3. Trigger Zaps from webhooks (opens in a new tab)Zapier Help · help.zapier.com
  4. Form webhook setup (opens in a new tab)Framer Help · framer.com
  5. Endpoints (opens in a new tab)Astro docs · docs.astro.build
  6. Environment variables (opens in a new tab)Next.js docs · nextjs.org

Checked against the official docs on. Tools change often; we re-check before every build.

Press Escape to close.

Zapier integration at a glance
ComplexityLow
Method
  • Framer: Zapier or Make
  • Webflow: Zapier or Make or Native
  • Astro: API
  • Next.js: API
Typical setup2 to 4 hours per flow
What we doWe connect the form, build and test the Zap, map fields cleanly and hand it over in your Zapier account.
CategoryAutomation

Setup by platform

How we set up Zapier

  • Framer

    • Zapier or Make

    There is no Zapier app for Framer. We add a Webhook destination to the Framer form and paste a Webhooks by Zapier Catch Hook URL. Framer sends the fields as JSON and retries up to five times on errors.

  • Webflow

    • Zapier or Make
    • Native

    Zapier’s Webflow app triggers on New Form Submission, New Order and comments, and can create or update CMS items. The form shows up in Zapier only after it is published and has one real submission.

  • Astro

    • API

    An on-demand server endpoint (prerender = false) validates the form and posts JSON to the Catch Hook. The hook URL stays in a server-only secret.

  • Next.js

    • API

    A Route Handler or server action posts to the Catch Hook, with the URL in a non-NEXT_PUBLIC environment variable so it never reaches the browser.

Use cases

What teams use it for

  1. Lead alerts

    A new demo request posts to a Slack channel and lands in the CRM within seconds.

  2. Forms into the CMS

    A submission becomes a Webflow CMS item, like a listing or job post, to review and publish.

  3. Order follow-up

    A new Webflow Ecommerce order starts fulfilment steps, invoices or a welcome email.

Before you add it

What to watch out for

  • Security

    Treat the hook URL as a secret

    A Catch Hook URL is protected only by being hard to guess. On coded sites it lives on the server; on Framer it sits in the form settings, not the page.

  • Limits

    Renames break triggers

    Renaming a Webflow site or form can make Zapier return 400 or 404 errors until the form is reselected. Webflow plans also cap webhook requests.

  • Data layer

    Name fields before launch

    Zaps map fields by name. We name form inputs clearly before launch, so a later copy change doesn’t silently break the mapping.

FAQ

Questions about Zapier

Adrian

Can't find your answer?

Book a call and let's talk.

Or email us hello@designme.agency

Is there a Zapier app for Framer?

No. Use the Framer form’s Webhook destination with a Webhooks by Zapier Catch Hook URL. It works on every form and needs no plugin.

Why doesn’t our Webflow form show up in Zapier?

Zapier only sees a Webflow form after it is published and has received at least one real submission. Submit a test entry on the live site, then reload the trigger.

Zapier or Make?

Zapier is quicker for linear flows and has the larger app catalogue. Make is better for branching logic and high volume. We use whichever your team already pays for.

You've reached the end, so now…

Tell us what you’re building.

We’ll help you map the right scope, team, timeline, and next steps.

Book a call