- Home
- Resources
- Integrations
- Webflow
Webflow Zapier integrationAutomate Webflow with Zapier.
The Webflow Zapier integration gives you 5 triggers, 7 actions and 2 searches to connect your site's forms, CMS content and orders to the rest of your stack of tools. Here is what each one does, what it costs you and where it fails.
Verified Trustpilot reviews · AI, automation & growth agency
What the Webflow Zapier integration actually does
Webflow is a tool for designing and running websites, with a built-in content manager (the CMS), and on Zapier it also exposes the orders a site receives. Linking it to Zapier lets what happens on your site, a form, an order, a comment, start work in other apps, and lets other apps write content back into your CMS collections.
Three outcomes cover most setups. Leads that never sit in a dashboard: New Form Submission sends every contact form to your CRM, your inbox or a sheet. A CMS fed from elsewhere: Create Item and Update Item turn rows from a spreadsheet or entries from another tool into blog posts, job offers or product pages. Orders handled without the Webflow dashboard: New Order passes each sale to your accounting or shipping tools, and Fulfill Order marks it as fulfilled when your side of the work is done.
Good news for free-plan users: four of the five triggers are instant, so forms, comments and orders reach Zapier the moment they happen. Only New Resolved Comment Thread waits for Zapier's next check.
What Zapier does not do for Webflow: there is no action to delete an item, and no way to create a form, a site or a collection. Every action works inside collections that already exist. To weigh other options, see the Webflow Make integration and the Webflow n8n integration.
Zapier vocabulary in one minute
Eight words come back throughout this page. Read them once and the rest flows.
- Zap
- The automation you build: one event that starts it, then one or more steps that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, for example a visitor sending your contact form.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like adding a CMS item.
- Task
- The unit Zapier bills. One task is one action that completed successfully, and your plan sets how many you get each month.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer; an instant one is pushed by the app as it happens. Webflow has four instant triggers and one polling.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and quietly stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, such as a CMS item, so the following steps can use it.
- Connection
- Your Webflow account linked to Zapier once, then reused by every Webflow step in every Zap you build afterwards.
What a Webflow Zap really costs
Zapier counts tasks, not Zaps, and on Webflow most triggers do not even need a check.
- Trigger checksFree of charge
- Successful action1 task each
- Failed actionNot counted
- Free plan100 tasks a month, two-step Zaps
The trigger never costs a task, and Zapier looking for new data is free too, however often it checks. Each action that goes through counts as one task, and in a Zap with three actions each one counts separately. An action that fails is not billed. Webflow is not a premium app, so it runs on the free plan: 100 tasks a month and unlimited Zaps, but only two steps, one trigger and one action. Add a filter, a search step such as Find Item or a second action, and the Zap is multi-step, which needs a paid plan.
Connect your Webflow account to Zapier
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. You need a Webflow account, plus access to any client site you did not build yourself but want the Zap to touch.
- 02
Pick Webflow
Type Webflow into the search box of the dialog, select it, then click Add connection. A new tab opens where you sign in to Webflow with the account that owns or edits the site.
- 03
Grant access
Allow Zapier to access that account. The connection then shows in your list, and every Webflow step you add later, in any Zap, can reuse it, so this part is done once.
Your first Webflow Zap, step by step
GoalEach time a visitor sends the contact form on your Webflow site, the details land in your CRM as a new contact, with no export to run.
- 01
Create the Zap
In the editor, pick Webflow as the app that starts things and New Form Submission as the event, then choose your connection, the site and the form to watch.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent submissions of that form. Fill in the form on your live site first if none exist yet, so you work on a real one.
- 03
Add your CRM
Add the app that should receive the lead as the second step, choose the action that creates a contact, and map onto it the form fields the trigger test actually brought back.
- 04
Test, then publish
Run the action test and check the contact shows up in your CRM. Then click Publish. Because this trigger is instant, the next form arrives straight away.
The 5 Webflow triggers
5 events start a Zap when something happens in Webflow, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.
New Form Submission
Instant triggerIn Zapier“Triggers when a new form submission occurs”
Someone filling in a form on your Webflow site starts this Zap with that submission. Forms are where leads, quote requests and sign-ups come in, which makes this trigger a natural first Zap.
New Comment
Instant triggerIn Zapier“Triggers when a new comment is created.”
A fresh comment left on your Webflow site sets this Zap off, which helps teams who review pages together and do not want feedback to sit unread.
New Order
Instant triggerIn Zapier“Triggers when a new order is placed.”
Each order placed on your Webflow site kicks off this Zap with the order details. It is the entry point for everything that should happen after a sale without someone watching the Webflow dashboard.
New Resolved Comment Thread
Polling triggerIn Zapier“Triggers when a comment thread is resolved.”
When a comment thread on your site is marked as resolved, this Zap picks it up and passes it on. It is the closing half of the review loop: you learn that a piece of feedback has been dealt with.
Updated Order
Instant triggerIn Zapier“Triggers when an order is updated.”
Any change to an existing order on your site starts this Zap, so the tools downstream stay in step with what Webflow now shows for that sale.
The 7 Webflow actions
Webflow gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Item
ActionIn Zapier“Adds a new item to a given collection.”
Adds a new entry to one of your CMS collections, ready to appear on the site at your next publish.
Create Live Item
ActionIn Zapier“Adds a new item to a given collection on your published site.”
Puts a new collection entry straight onto your published site, without waiting for anyone to hit publish in Webflow.
Fulfill Order
ActionIn Zapier“Fulfills an order.”
Marks an order as fulfilled in Webflow, and lets you decide whether the customer gets the Order Fulfilled email.
Update Item
ActionIn Zapier“Updates an item.”
Edits an entry that already exists in a collection, so the CMS follows changes made in another tool.
Update Live Item
ActionIn Zapier“Updates a live item.”
Changes an entry on the published version of the site, and can also mark it as archived instead of leaving it active.
Update Order
ActionIn Zapier“Updates an order.”
Modifies an existing order on your Webflow site from information that lives in another app.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
An advanced step that sends a raw request to Webflow with your existing connection, for whatever the ready-made actions do not offer.
The 2 Webflow searches
2 search steps look for data that already exists in Webflow, so a later step can use it.
A search step finds something already in Webflow and hands it to the next steps. In the list of action events, searches sit at the bottom under their own SEARCH heading. Webflow has no find-or-create entry, but the three settings below still decide what happens when a search surprises you.
Find Item
SearchIn Zapier“Find an Item in a Collection.”
Looks up an entry inside one of your CMS collections and returns it, so a later step can edit it or reuse its content.
Find Live Item
SearchIn Zapier“Find a Live Item in a Collection.”
Searches the published version of a collection rather than the working copy, which is what you want before touching what visitors see.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips what depended on it. Switched on, the Zap carries on without a result.
- Create X if it doesn't exist yet?On apps that offer it, ticking this box creates the missing item instead of stopping. Webflow's two searches do not come with a find-or-create entry.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Webflow Zap breaks
Webflow Zaps tend to fail for a handful of reasons. Spotting them early saves you a lost lead or an unshipped order.
Zapier links a help article called Common Problems with Webflow on Zapier to this app. The cases below come from the limits every Zap shares and from the Site and Collection fields almost every Webflow step requires. When a Zap stops and you cannot see why, start with our Zapier troubleshooting page.
Old forms and orders never arrive
A Zap only reacts to what happens after you switch it on. Submissions and orders from before stay in Webflow, and moving that backlog is a separate job.An order Zap restarts itself
A Zap that runs Update Order on the same site its own Updated Order trigger watches can set itself off again and again, eating through your tasks fast.A bulk import gets held back
When a trigger suddenly returns a huge batch, after a migration for example, Zapier's flood protection can hold it back.Site or collection out of reach
Most steps require a Site, and CMS steps a Collection too. The step can only be set up on a site the connected account has access to, so check that access first.
Need help automating Webflow with Zapier?
A person reads every message.



