Resources · Zapier integration

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

Overview

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.

Vocabulary

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.
Cost

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

Connect your Webflow account to Zapier

  1. 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.

  2. 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.

  3. 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.

First Zap

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

Triggers

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.

1

New Form Submission

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sending each quote request to your CRM and pinging the sales team in chat.
Watch out
you pick one site and one form, so a second form needs its own Zap.
2

New Comment

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
turning each review comment into a task in your project tool so nothing slips before launch.
Watch out
the site is required, so one Zap follows one site.
3

New Order

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
creating the invoice in your accounting tool and the shipping label in your logistics app.
Watch out
one Zap watches the orders of one site.
4

New Resolved Comment Thread

Polling trigger

In 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.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
ticking off the matching task in your project tool once a fix is approved.
Watch out
it is the only Webflow trigger that waits for a check.
5

Updated Order

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
updating the status of a sale in your spreadsheet or CRM when the order changes.
Watch out
a Zap that edits orders itself, through Update Order, can set this trigger off again.
Actions

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.

1

Create Item

Action

In 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.

When to use it
a row added to a job-offers spreadsheet becomes a careers page item.
Watch out
the Is Draft option keeps it hidden; by default the item is not a draft.
2

Create Live Item

Action

In 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.

When to use it
event listings or news that must be visible as soon as they are approved elsewhere.
Watch out
check the content twice, because it goes live for every visitor.
3

Fulfill Order

Action

In Zapier“Fulfills an order.”

Marks an order as fulfilled in Webflow, and lets you decide whether the customer gets the Order Fulfilled email.

When to use it
your order-handling tool reports an order as done and Webflow marks it fulfilled without anyone opening it.
Watch out
the email choice is required, so think about it before testing on a real customer.
4

Update Item

Action

In Zapier“Updates an item.”

Edits an entry that already exists in a collection, so the CMS follows changes made in another tool.

When to use it
a price changed in your product sheet is copied to the matching Webflow item.
Watch out
the item is required, so pair it with Find Item when you do not have its identifier.
5

Update Live Item

Action

In 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.

When to use it
archiving a job offer the moment the position is filled in your hiring tool.
Watch out
archiving is not deleting, and no Webflow action on Zapier deletes an item.
6

Update Order

Action

In Zapier“Updates an order.”

Modifies an existing order on your Webflow site from information that lives in another app.

When to use it
bringing a change made in your order-handling tool back onto the Webflow order.
Watch out
it needs the order identifier, which an earlier step has to supply.
7

API Request (Beta)

Action

In 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.

When to use it
only if Webflow's developer documentation does not put you off.
Watch out
requests only reach Webflow's own domains, and the Stop on error choice decides whether a failure halts the Zap.
Searches

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.

1

Find Item

Search

In 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.

When to use it
finding the product item to edit before Update Item changes its price.
Watch out
site and collection are both required, so one search covers one collection.
2

Find Live Item

Search

In 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.

When to use it
locating the live job offer that Update Live Item should archive.
Watch out
like Find Item, it asks for a site and a collection.

The three settings every search exposes

  1. 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.
  2. 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.
  3. 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 it breaks

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

Need help automating Webflow with Zapier?

A person reads every message.

FAQ

Webflow Zapier integration: common questions

01Is the Webflow Zapier integration free?
Yes, Webflow is not a premium app on Zapier, so it works on the free plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps, one trigger and one action. A Zap that sends a form to your CRM fits. As soon as you add a filter, a search such as Find Item or a second action, the Zap becomes multi-step and requires a paid Zapier plan.
02How many Zapier tasks does a Webflow Zap use?
One task per action that succeeds, and nothing for the trigger. Receiving a form or an order costs nothing; it is what the Zap does next that counts. A Zap that creates a CRM contact for every form uses one task per submission. If the same Zap also posts a chat message, that is two tasks per form. An action that fails is not billed, so a broken step does not eat into the 100 monthly tasks of the free plan.
03Does Webflow trigger Zaps in real time?
Mostly, yes. New Form Submission, New Comment, New Order and Updated Order are instant: Webflow tells Zapier the moment they happen, on every plan, free included. New Resolved Comment Thread is the exception. It is a polling trigger, checked every 15 minutes on the free plan, every 2 minutes on Professional and every minute on Team and Enterprise. For forms and orders, you get immediate reactions without paying for speed.
04What does it take to connect Webflow to Zapier?
A Webflow account and a Zapier account. You open the Apps page in Zapier, click + Add connection, search for Webflow, sign in in the tab that opens and grant access. The account matters: almost every step asks you to choose a Site, and CMS steps also need a Collection. If you work on a client's site, make sure the account you connect has access to it, since every step needs that site.
05What is the difference between Create Item and Create Live Item?
Create Item adds an entry to a CMS collection, and it appears on the site at the next publish. Create Live Item puts the entry straight onto the published site. The same split exists for updates, Update Item and Update Live Item, and for searches, Find Item and Find Live Item. Use the plain version when someone should review before going live, and the live version only when the content is already approved.
06What if the Webflow action you need does not exist?
Look at API Request (Beta). It is an advanced action that sends a raw request to Webflow using the connection you already set up, which can reach what the six ready-made actions leave out. It only reaches Webflow's own domains, and you choose whether an error stops the Zap. It does assume you are comfortable with Webflow's developer documentation, a clear step up from choosing an action in a list.
07Zapier, Make or n8n for Webflow?
There is no single winner, only criteria. On Zapier, Webflow offers the 14 operations on this page: four of the five triggers are instant, every successful action is billed as a task, and multi-step Zaps need a paid plan. What Make and n8n offer for Webflow is covered on their own integration pages, not here. Compare on three points: whether the operation you need exists, how many steps your flows need, and which tool your team already runs.