How Do I Send Webflow Form Submissions to Airtable Without Zapier?

How do I get Webflow form leads into Airtable without paying for Zapier?

You use a webhook. Webflow can send each form submission straight to Airtable, and Airtable can catch it and create a record, with no Zapier in the middle. Webflow posts the data, Airtable receives it, and a record appears in your table. The only cost is a paid Airtable plan, since the webhook trigger is not on the free tier.

I lean on Airtable for real production work, not toy demos. The Airtable and WhaleSync system I run for Ajust has delivered more than 25,000 cases, so I have a strong bias toward getting data into Airtable cleanly. A direct webhook is the simplest way to do that for a Webflow form, and it removes a monthly bill you do not need.

This tutorial walks through the whole path in plain steps: what you need first, how to set the webhook in Webflow, how to catch it in Airtable, how to map your fields, and how to test it. By the end you will have leads flowing from your site into a table you can actually work with.

Why send Webflow forms to Airtable at all?

Because a Webflow form on its own is a dead end for real work. Submissions land in the Forms panel and in your inbox, which is fine for a trickle but painful at volume. Airtable turns those submissions into a live database you can filter, tag, assign, and build views and automations on top of. It is where a lead becomes a workflow.

Once the data is in Airtable, the whole operation opens up. You can route a lead by type, track its status through a pipeline, trigger follow up emails, or sync it onward to other tools. None of that is possible while your leads sit as flat email notifications. The form is the front door, and Airtable is the room where the work happens.

This is the same reason people push Webflow forms into other tools too. I have written about sending them to a Notion database without Zapier for teams that live in Notion. Airtable is my pick when the goal is structured records, filtered views, and automation, which is most business cases.

What do I need before I start?

You need three things: a Webflow site on a plan that allows form webhooks, a paid Airtable account, and an Airtable base with a table ready to receive the data. The table should have a column for each form field you care about, like name, email, and message, so there is somewhere for each value to land.

Plan your columns before you touch any settings. I sketch the table first and decide exactly which fields the form will send and what type each column should be. A short text field for a name, an email field for the address, and a long text field for a message is a typical start. Getting this right upfront saves rework later.

It also helps to name your form fields clearly inside Webflow. The webhook sends whatever field names you set, so a field named "Email Address" arrives as that exact label. Clean, predictable names make the mapping step in Airtable far easier, because you are matching obvious labels instead of guessing at cryptic ones.

How do I set up the webhook in Webflow?

In Webflow, open your site settings and find the integrations area, then the webhooks section. Add a new webhook, choose form submission as the trigger, and paste in the webhook URL that Airtable will give you. Once saved, every matching form submission on your site fires a POST request carrying the form data to that URL.

There is an order of operations issue here worth flagging. Webflow wants a URL to send to, but that URL comes from Airtable, which you set up in the next step. So in practice you start the Airtable automation first, copy the URL it generates, then come back to Webflow and paste it in. I always build the Airtable side before I finish the Webflow side.

Webflow also exposes this through its Data API and its webhooks reference, if you prefer to manage it in code. For most business owners the site settings path is enough, and it needs no code at all. Either way, the trigger you want is form submission, which is what carries a lead's answers out of Webflow.

How do I catch the webhook in Airtable?

In Airtable, open your base, go to Automations, and create a new automation. Set the trigger to "when webhook is received." Airtable then generates a unique webhook URL for you. That URL is the one you paste back into Webflow. This trigger is the piece that lets Airtable listen for incoming data on its own, with no third party service.

Copy that generated URL carefully, because it is the bridge between the two tools. Anything Webflow posts to it will be captured by this automation. Treat the URL as a secret, since anyone who has it could send data into your base. I keep these URLs out of public documents and only paste them where they belong.

Remember that this trigger lives behind a paid Airtable plan. The free tier does not include the webhook trigger, so if you are on it, you will need to upgrade before this works. That paid plan is the only real cost of the whole setup, and it replaces the recurring fee you would otherwise pay a connector service.

How do I map the form fields to Airtable columns?

After the trigger fires once with real data, Airtable can see the shape of the incoming payload. You then add a "create record" action, choose your table, and match each form field from the webhook to the matching column. The email value maps to your email column, the name to your name column, and so on down the list.

This is the step where clean field names pay off. Airtable shows you the incoming values by their labels, and you point each one at the right column. If a value is buried inside the payload, you may need to reference it by its path, which is why testing the trigger first, so Airtable has a real example to read, makes this far smoother.

Take a moment to match data types too. A date coming from a form should land in a date column, and a number in a number column, or Airtable may store it as plain text. Getting the types right here keeps your views, filters, and later automations working the way you expect instead of breaking on a stray text value.

How do I test that it works?

Submit your real form once, then open the Airtable automation and run its test. Airtable will show whether it received the webhook and created the record, usually with a clear success message. Check that a new row appears in your table with the right values in the right columns. Do not trust the setup until you see a real submission land.

I always test with a submission that looks like a real lead, not the word "test" in every field. Realistic data surfaces mapping mistakes that placeholder junk hides, like a phone number landing in the wrong column or a date arriving in an odd format. One honest test submission is worth ten lazy ones.

If nothing arrives, work backward through the chain. Confirm the Webflow webhook points at the exact Airtable URL, confirm the trigger is form submission, and confirm the automation is turned on. Nine times out of ten the problem is a mismatched URL or an automation left switched off, both quick to fix once you check them.

When should I still use Make or a middleware?

Reach for a middleware when the data needs to change shape on the way in. If you have to reformat values, split one field into several, look something up, or fan the submission out to several tools at once, a tool like Make earns its place. The direct webhook is perfect for simple, one to one delivery, and clumsy for heavy transformation.

My rule is to start direct and add middleware only when a real need appears. A plain contact form going into one table does not need Make. A quoting form that must calculate a total, tag the lead, and notify a channel probably does. I described that kind of setup in my walkthrough of a Make automation for Webflow.

The point is to match the tool to the job. Paying for a connector to move a name and email into one table is waste. Paying for one to run real logic across several systems is fair. Knowing which situation you are in is most of the skill, and it saves both money and future headaches.

Should you build this yourself?

If your need is simple, yes, build it yourself. The direct Webflow to Airtable webhook is a one time setup that runs for free after your Airtable plan, and it replaces a monthly connector bill. Start the Airtable automation, paste its URL into Webflow, map your fields, and test with a real submission. That is the whole job.

The bigger lesson is that a lot of "you need Zapier" advice is just habit. Many tools now speak webhooks natively, and stitching them together directly is cheaper and often more reliable, since there is one less service to break. I default to native connections first and only add a paid layer when the work truly calls for it.

If your form logic is more involved, or you want a clean Airtable base that actually drives your operations, I am happy to design it with you. Building reliable automation pipelines is a core part of what I do, and every business needs a slightly different shape. Tell me what your leads should trigger and let's connect.