Zapier Webflow Integration

Overflow builds your Webflow site and connects it to the rest of your stack with Zapier, so every form submission and CMS update lands where it should. Book a call. We're an official Certified Webflow Partner.

Leads sit in Webflow's Forms tab. Someone copies them into the CRM by hand on Friday afternoon. Or a Zap stopped working weeks ago, and nobody noticed until sales asked where the demo requests went.

Zapier connects Webflow to more than 7,000 apps through trigger and action workflows called Zaps. One Webflow form submission can create a HubSpot contact, post a Slack message and add a Google Sheets row, without code.

Setting up a Zap takes minutes. Keeping it working is the real job. Forms get renamed. Webhooks get deactivated. Free plans poll every 15 minutes. And a failed Zap doesn't always throw an error you'll see. That's what we engineer for.

• Route every lead to the right tool, complete and on time.
• Know when a Zap fails, and who fixes it.
• Change forms and automations without waiting for a developer.

Let's talk, or see how we approach Webflow integrations.

Why a Zap that works in testing still loses leads

The old way: someone connects Zapier in an afternoon, tests one submission, and nobody owns it after that. The first sign of trouble is sales asking where the leads went.

The Overflow way: the Zap is part of the website build. Every trigger, field, destination and failure path is mapped, tested on the live site and documented for marketing.

Here's what breaks Zaps in practice. All of it is documented by Webflow and Zapier themselves:

• Renamed forms. Renaming a form or site in Webflow can break a connected Zap until someone reselects it in the trigger step.
• Deactivated webhooks. Webflow retries a failed webhook delivery up to 3 times at 10-minute intervals. After that, the webhook is switched off.
• Polling delays. On Zapier's Free plan, every trigger falls back to 15-minute polling, even the ones labelled Instant.
• Task limits. Every successful action uses a task. On the Free plan, 100 tasks a month is the ceiling. On paid plans, extra tasks are billed as you go unless you've turned that off, so the limit shows up as a stopped Zap or an unexpected invoice.

Who this is for

B2B marketing leads and founders on Webflow, or moving to Webflow, whose leads and content need to reach a CRM, an email tool, Slack, Google Sheets or Airtable. The trigger is usually a new site, a new CRM, a new market or a team that has outgrown copy-paste.

Where it needs a plan

Zapier is one more system, with its own cost per task and its own owner. If a native Webflow app does the job, we use that instead. For a single destination, the Webflow HubSpot integration or the Webflow Mailchimp integration is often simpler.

What can you automate with Webflow and Zapier?

Webflow forms, CMS items, comments and ecommerce orders can all trigger or receive Zaps. For a B2B site, three use cases matter most: routing leads, notifying your team and feeding the CMS. Order triggers and actions exist too, but we don't build ecommerce sites, so we leave those out here.

Route form submissions to your CRM and email tools

A Webflow form can send its data to HubSpot, Salesforce, Pipedrive, ActiveCampaign, Mailchimp or a Google Sheet. Zapier has pre-built templates for most of these, and Webflow's Help Center says form data can reach hundreds of apps this way. Want the dedicated setup per tool? See our Webflow Salesforce integration, Webflow Pipedrive integration, Webflow ActiveCampaign integration and Webflow Google Sheets integration.

Notify sales the moment a lead comes in

A demo request posts to a Slack or Microsoft Teams channel, or creates a task for the account owner. Sales sees it while the buyer is still on your site. One condition: instant delivery needs a paid Zapier plan. More on that below.

Create and update CMS items from Sheets, Airtable or Notion

Webflow's own example: a new Google Sheets row creates a new blog post in a CMS collection. The sheet needs a column for every collection field, and dates must follow the API format.

You choose how it lands. Create Item adds a draft for review. Create Live Item publishes straight to the live site. We pick per workflow, and add a review step when content should be checked first. CMS work needs a CMS Site plan or higher. Read more about Webflow CMS collections, our Webflow Airtable integration and Webflow Notion integration, or how this scales into programmatic SEO in Webflow.

Store file uploads and back up submissions

Files uploaded through a form can go to Google Drive. To make that work, Webflow requires you to turn off login security for uploaded files. That's a decision, not a default: it changes who can open those files. We make it with you, per form.

How does the Webflow Zapier integration work?

A Zap starts with a trigger, an event in one app, and runs one or more actions in other apps. A visitor submits your demo form (trigger). Zapier creates the CRM contact and pings Slack (actions).

The Zapier app in the Webflow Marketplace connects through OAuth. You can limit access to specific sites or Workspaces, and Zapier never gets your Webflow password.

According to Webflow's Zapier integration page, the native connector offers:

• 5 triggers: New Form Submission, New Order, Updated Order, New Comment and New Resolved Comment Thread.
• 7 actions: including Create Item, Create Live Item, Update Item and Update Live Item.
• 2 searches: Find Item and Find Live Item.
• API Request (Beta): a raw HTTP request that uses your Webflow connection, for operations the connector doesn't cover.

What's missing: the native connector has no Delete Item or Publish Site action. Deleting CMS items or bulk publishing needs the API Request action or a direct call to the Webflow API.

Two requirements come before any form trigger works. The form must be published on a live domain, because Preview mode doesn't fire triggers. And at least one submission must exist, so Zapier can detect the form and map its fields. A test submission counts.

What you get when Overflow sets up your Zaps

You don't get a Zap someone clicked together. You get automations that are mapped, tested on the live site and documented, so your team knows where every submission goes.

Map every trigger before we build

For every form and CMS event, we write down what it represents (demo request, download, newsletter, event signup), which fields move, where they go and who follows up. It's the same rule we use for every Webflow integration: trigger, fields, permissions, transformations, destination, failure handling and owner, mapped before anything is installed.

Choose the right trigger speed and plan

On paid Zapier plans, New Form Submission, New Order, Updated Order and New Comment fire immediately. On Free, triggers poll every 15 minutes. For a newsletter signup, that's fine. For a demo request, it isn't.

We size your Zapier plan to real volume. Each successful action counts as a task. Triggers and Zapier's checks for new data don't.

Plan for what happens when a Zap fails

Native Webflow forms keep a copy of every submission in Webflow, so there's always a record to fall back on. Webhooks are less forgiving: after 3 failed deliveries at 10-minute intervals, Webflow deactivates the webhook and emails the site owner. We decide upfront who receives that email and Zapier's error notifications, and who checks them. Every Zap gets a named owner and a fallback in the handover docs.

Build forms and CMS fields that map cleanly

Every form gets a unique name and clear field labels. Reusable form components carry hidden fields that pass page context, such as which service, event or resource the lead came from. Since Webflow's v2 API, a form component reused across pages can show up in Zapier as separate forms, so we check how Zapier sees each instance and use a webhook where one trigger has to catch them all.

We also design around CMS realities. Reference and multi-reference fields can't be mapped in Zapier's standard create and update actions. Option field values must match Webflow exactly, capitalisation included. Dates need the ISO format the API expects. Where needed, we add a Formatter step, use the API Request action or change the structure. Read more on Webflow forms and the Webflow CMS.

Pass campaign data with every lead

Hidden fields carry UTM and source data through the Zap into your CRM, so marketing can tie a contact to the campaign that brought them in. We tell you upfront which attribution your setup supports, and which it doesn't.

Respect consent and data protection

Webflow's Help Center reminds site owners to review their responsibilities as a data controller when they send personal data to tools like Zapier. We build forms and flows with that in mind. For the legal side, check with your own advisor.

Hand it over to marketing

You get documentation of every Zap (trigger, steps, owner, fallback), live training and video walkthroughs. Ownership, not dependency: the Zapier account, the Webflow site and the docs are yours.

What usually breaks, and how we prevent it

• Zap stops after a form is renamed. Renaming a form or site can break the trigger. The fix is to reselect site and form in the trigger step, and that check is in our handover docs.
• Form doesn't appear in Zapier. It isn't published on a live domain, or there's no submission yet. We publish and submit a test before connecting.
• Leads arrive 15 minutes late. That's Free plan polling. We match the plan to how fast sales needs to respond.
• Zaps stop or costs jump mid-month. The task limit was reached. We estimate use as action steps per Zap times monthly runs before choosing a plan.
• CMS items arrive as drafts, or go live too early. Create Item and Create Live Item got mixed up. We choose deliberately per workflow.
• Webhook silently deactivated. Three failed deliveries switch it off. Error notifications go to a named owner, not a shared inbox nobody reads.
• Zaps broke after a Webflow API update. Webflow deprecated its v1 API on March 31, 2025, and Zaps had to be reconnected. We build on the current Webflow app version.

Zapier, a native app or the API: which connection fits?

Our rule: use the least complex method that meets the requirements. Here's how the options compare.

• Native Webflow app. Best when one tool is the only destination, such as HubSpot or Mailchimp. No extra system to pay for or maintain.
• Zapier with the native Webflow connector. Best when one event must reach more than one tool, or when the tool has no native Webflow app. The trade-off: cost per task and one more system to look after.
• Zapier Forms in a Code Embed. Zapier-hosted forms skip Webflow's form storage and support conditional logic on paid Zapier plans. But Zapier controls the styling, with limited CSS. We default to native Webflow forms, so your forms match your design system.
• Webhooks by Zapier. For Webflow events the connector doesn't expose, such as a new CMS item or a site publish.
• Webflow API or the API Request action. For deletes, publishing, bulk operations and custom transformations. It takes development time and upkeep, often with custom code.
• Make or n8n. Alternatives we consider when they fit your data flow better.

We choose in strategy, based on your data flow, your tools and your volume. Not on habit.

Is Zapier worth it for a B2B Webflow site?

Yes, when leads or content must reach several tools and no native app covers it. No, when one native integration does the job.

On cost, Zapier's pricing page lists a Free plan with 100 tasks per month. Each successful action is a task. Checking for new data isn't. The Free plan only runs two-step Zaps, one trigger and one action, so multi-step workflows need a paid plan. Third-party breakdowns from NoCode MBA and others put the entry paid plan at $19.99 a month billed annually. Prices change, so check Zapier's current pricing before you commit.

A quick example: a Zap that creates a CRM contact, posts to Slack and adds a sheet row uses 3 tasks per submission. Thirty demo requests a month means 90 tasks for that Zap alone, and the three actions already put it on a paid plan.

Moving to Webflow without breaking the automations you already run

Moving from WordPress, HubSpot CMS or a custom CMS? Your old site probably runs on form plugins, embedded handlers and Zaps nobody has looked at in a while. On launch day, those all disappear with it.

So before the move, we list every form handler, plugin and Zap on your current site. Each one gets rebuilt on Webflow forms and reconnected to the same destinations, then tested on the live domain. Lead flow doesn't stop when the new site goes live.

We protect your SEO equity at the same time: URL mapping, 301 redirects, metadata and schema carried over. Read more about Webflow migration, WordPress to Webflow migration and our Webflow SEO services.

How fast? Nedcargo moved from WordPress to Webflow in 4 weeks. Most builds take six to eight weeks. We agree your timeline after discovery.

How we deliver your Webflow Zapier integration

Same six steps as every Overflow project, with the automation layer built into each one.

1. Strategy and discovery. We audit your current site, forms, tools and existing Zaps, and write the data flow plan.
2. Scalable design system. Form components and their states (default, error, success) designed in Figma.
3. Webflow development. CMS, components, forms and the Zaps chosen in strategy.
4. Content migration. Content, redirects and technical SEO, with AI Search built in.
5. Quality assurance. Test submissions from the live site, Zap run history, error notifications and consent behaviour.
6. Handover. Documentation, training and support.

Cost and timing are agreed upfront. As one client put it: "they keep their promises."

Proof from B2B teams we've built for

To be straight with you: we don't have a Zapier-specific case study to show yet. What we can show is how we build and migrate B2B Webflow sites, the foundation every Zap depends on.

• Nedcargo: WordPress to Webflow in 4 weeks, with a 98+ Lighthouse performance score.
• BlinkLab: 7 weeks from strategy to launch, built for its next growth phase after a $17.5M raise.
• Aumatics: 300%+ marketing ROI and 8+ new high-ticket clients.

"Communication was always smooth and fast, the quality of their work was excellent." Marketing Manager, Informer Group

"They keep their promises." Quinten van der Kraaij

Who does the work

Overflow is an official Certified Webflow Partner. Jort Steinebach, Certified Webflow Developer with 40+ Webflow sites, leads development and integrations. Niels Voshol covers strategy, SEO and AI Search across 40+ B2B projects. A small senior team, with no handoff to juniors. See how we work as a B2B Webflow agency.

What does a Webflow Zapier integration cost?

There's no price list. We scope your setup and agree a fixed price before we start.

What drives the scope

• The number of forms and Zaps.
• The number of destination tools.
• Form routing only, or CMS syncing as well.
• Custom webhooks or API work.
• A standalone setup on your existing Webflow site, or part of a build or migration.
• Languages and markets, with Webflow localization.

Third-party costs you own

• A paid Webflow Site plan. The free Starter plan is limited to 50 form submissions in total, and that limit doesn't reset. CMS automations need a CMS plan or higher.
• Your Zapier plan, sized to your task volume.
• Your destination tools' own plans. Some apps count as premium on Zapier and need a paid Zapier plan.

Fixed scope, cost and timing upfront. No funnies, no surprises. Let's talk about your setup.

Webflow Zapier integration FAQ

Does Webflow integrate with Zapier?

Yes. Webflow has a Zapier app in its Marketplace that connects through OAuth. Zaps can run on form submissions, comments and orders, and can create or update CMS items.

Do I need a paid Webflow plan to use Zapier?

Zapier's help center lists the free Starter plan or any paid Site plan for the connection, but CMS collections need a CMS plan or higher. Starter is also capped at 50 form submissions in total, so a paid Site plan is the realistic starting point.

Why isn't my Webflow form showing up in Zapier?

The form must be published on a live domain and have at least one submission. Submit a test on the live site, then refresh the trigger in Zapier.

Are Zapier's Webflow triggers instant?

Only on paid Zapier plans. On Free, all triggers poll every 15 minutes, and New Resolved Comment Thread always polls.

Can Zapier trigger when a Webflow CMS item is published?

Not with the native connector. Use Webhooks by Zapier with a Webflow webhook for CMS events or a site publish.

Can Zapier fill reference and multi-reference fields?

Not through the standard CMS actions, per Zapier's help center. It needs a workaround, such as an API request that passes stored Webflow item IDs, which we only use when the content model needs it.

What's the difference between Create Item and Create Live Item?

Create Item adds a draft to the collection for review. Create Live Item adds it straight to the published site.

Is Zapier GDPR compliant?

Zapier states it is SOC 2 Type II certified and GDPR compliant, acting as a processor, but you remain the data controller for the personal data you send through it. We configure flows with that in mind. Check legal questions with your own advisor.

Do you only set up Zaps, or build the whole site?

We can connect Zapier to an existing Webflow site. Most clients have us build or migrate the site and engineer the automations as part of it, so forms, CMS and Zaps are designed together.

Ready for automations your team can trust?

Your website shouldn't be where leads go missing. Webflow runs the site. Your CRM runs the pipeline. Zapier moves the data. And every step has an owner who knows when something breaks.

Want to be cited in ChatGPT, Gemini, Perplexity and AI Overviews too? See our AEO agency work, or browse all Webflow integrations.

Let's talk. Book a call and we'll map your setup together.