When your WooCommerce store is small, copying order details into Airtable is manageable. When order volume grows, it stops being a minor task and becomes a daily process. Someone checks the orders, copies the customer name, email, phone, product, and payment method, and pastes everything into the right Airtable table. Do it for ten orders. Then fifty. Then two hundred.
At that point, it is not a task. It is a job that takes time away from running the store. The fix is straightforward. Every new WooCommerce order can automatically create an Airtable record, including customer details, product name, and order total, without anyone having to touch it manually.
This guide shows you how to set up an Airtable WooCommerce integration using Bit Flows. WooCommerce is the trigger. Airtable is the action. The setup takes under 20 minutes and requires no code.
With Bit Flows, a new WooCommerce order can automatically create a new record in Airtable.
Set WooCommerce: On New Order Create as the trigger and Airtable: Create Record as the action. Then connect Airtable with a Personal Access Token, select your base and table, and map fields like customer name, email, phone, product name, payment method, and order total.
Use this setup when you want every WooCommerce order stored in Airtable so your team can track orders, review customer details, manage fulfillment, and keep sales data in one organized table.
Before setting up the integration, it helps to understand what the final workflow will do. The workflow looks like this:
In this tutorial, WooCommerce starts the automation; the trigger determines when the workflow starts. For this use case, the trigger is: WooCommerce → On New Order Create
When a customer places a new order on your WooCommerce website, Bit Flows captures the order details and sends the selected fields to Airtable. Airtable then creates a new record with the customer name, email, phone number, product name, payment method, and order total.
If you only need to track a subset of orders, for example, orders above a certain value or orders for a specific product, you can add a Condition node after the trigger to filter before the Airtable record is created.
This setup is easier if WooCommerce is already running on your WordPress site. Most store owners reading this probably already have it installed. If you haven’t installed it yet, follow the WooCommerce installation guide, then activate the plugin. After that, complete the basic WooCommerce setup and add one test product. This test product will help Bit Flows capture real WooCommerce fields later.
Next, install Bit Flows the same way and activate it. You’ll also need an Airtable account where the WooCommerce order records will be stored.
Once WooCommerce, Bit Flows, and Airtable are ready, you can start building the workflow.
Open your Airtable account and create a new base or open an existing one. For example, Base name: Website Leads CRM. Add these fields:
Keep Full Name as a single-line text for the customer’s billing first and last name, Email as an Email field for the billing email, Phone as a Phone number field for the billing phone, and Product Name as a single-line text for the ordered product name.
Keep Payment Method as a single line of text for now. In your test, WooCommerce payment values came through as short gateway values, such as cod and bacs. If you use a Select field too early, Airtable may reject values that do not already exist as select options.
Once you know the exact payment methods your store uses, you can later convert this field to a Select field if needed. Keep Order Total as a Number field. This will store the final WooCommerce order amount. Using a number field makes it easier to sort, filter, or calculate order values inside Airtable.
Airtable requires a Personal Access Token to authorize the connection with Bit Flows. Legacy Airtable API keys can no longer access the Airtable API. Airtable completed the API key deprecation on February 1, 2024, so a Personal Access Token is required.
In Airtable, go to: Builder Hub → Developers → Personal access tokens → Create token
Token name: WooCommerce Orders to Airtable
Add these scopes:
These scopes are recommended in Bit Flows’ Airtable documentation for the Create Record connection. Without all four, the connection may fail or fields may not load correctly inside Bit Flows.
Under Access, select only:
Website Leads CRM
Limiting access to one base reduces risk. If this token is ever exposed, only that base is affected. Click Create token.
Airtable shows the token only once. Copy it immediately and store it in a secure note before closing the window.
Open Bit Flows from your WordPress dashboard. Click Create New Flow and name it: WooCommerce Orders to Airtable
In the Flow Builder, click the trigger node and configure:
After selecting the trigger, click Listen Response.
Now go to your WooCommerce store and place a test order. Use a real product and complete the checkout with your preferred payment method. Return to Bit Flows. You should see the captured WooCommerce order response. Confirm these fields appear in the response:
These are the fields you will map into Airtable in Step 5. If any field is missing, check whether the WooCommerce order was placed with all required billing fields completed.
After the WooCommerce trigger → go to Apps → search for Airtable → select Create Record.
Bit Flows’ Airtable documentation lists Create Record as one of the available Airtable events. It also supports Update Record, Delete Record, Search Record, and Get All Records, but for this workflow, Create Record is all you need.
Click Add Connection → paste your Airtable Personal Access Token from step 2 → name the connection: Airtable connection then Click Connect.
Once connected, select:
If you kept the default table name, select Table 1.
Field mapping tells Bit Flows which WooCommerce order value goes into which Airtable column. Map the fields like this:
Full Name mapping: Combine the first name and last name fields with a space between them. In Bit Flows, this looks like: {{billing_first_name}} {{billing_last_name}}. The result in Airtable will appear as a single full name.
Order Total mapping: Confirm the Airtable field type is set to Number. If it is set to single-line text, the value will be stored as a string, which means Airtable cannot calculate totals, averages, or use the field in formula columns later.
Click Test Run in the Airtable action node.
After the test completes, open Airtable and check your WooCommerce Orders table. A new record should appear with the values from your test order.
The values in your test will come from the order you placed in Step 3.
Bit Flows’ Test Run output appears above the test area, but Test Run results are not recorded in the flow logs. If you want to verify the complete workflow in the logs, including the trigger and the action together, use Listen Response, place a new test order, and let the full flow run. Then check the logs as described in Step 6.
Now, place a test order from your WooCommerce store, just like a normal customer would. Add the test product to the cart, complete checkout, and wait for Bit Flows to receive the new order data.
Once the order is created, Bit Flows will automatically run the workflow. It will capture the WooCommerce order details and send the mapped fields to Airtable. If everything is set correctly, a new record will appear in your Airtable table with the customer name, email, phone number, product name, payment method, and order total.
Then open the Bit Flows logs from the Flow Builder. The logs help you confirm whether the WooCommerce trigger fired, whether the Airtable action ran, which values were sent, and whether Airtable returned a successful response.
This step matters because the workflow can run, but wrong field mapping can still send data to the wrong Airtable column. Always compare the Airtable record with your WooCommerce test order before using the flow on real orders.
The WooCommerce trigger fires the moment an order is placed, not when it ships, not when it’s paid.
That timing matters. Your fulfillment team opens Airtable and sees the new order immediately, without waiting for someone to run an export or share a spreadsheet.
The Create Record action in Airtable removes the copy-paste step entirely. Order totals go into Number fields. Customer emails go into Email fields. Every record arrives clean, correctly typed, and structured the same way whether it’s order #1 or order #10,000 because the field mapping, not a team member, decides where each value lands.
The mapping also adapts to your store. If you collect custom billing fields, use product attributes, or capture order notes, you add those fields to the mapping without touching anything else in the workflow. Bit Flows captures all available WooCommerce order data in the Listen Response step, so every field the order contains is available to map.
A small WooCommerce store may receive 30 to 50 orders each week. Without automation, the owner has to send order details to the fulfillment team or ask them to check WooCommerce manually. With this workflow, every new WooCommerce order creates a record in Airtable with the customer name, product name, payment method, and order total. The team can open Airtable and start processing orders without waiting for a daily email or manual update.
A WordPress agency may manage several WooCommerce stores, and each client may use a separate Airtable base for order tracking. Instead of manually updating each client’s Airtable table, the agency can create one Bit Flows workflow per store. Each WooCommerce site sends order data to the correct Airtable base automatically.
Open your Airtable table after placing a test WooCommerce order. If a new record appears with the correct customer name, email, product, and order total, the workflow is working.
From that point forward, your team does not need to open WooCommerce to check incoming orders. If your store grows to the point where a simple record log is not enough, where you need to route high-value orders to a separate table, notify a fulfillment team on Slack, or update a customer record instead of creating a duplicate, those additions are all possible inside the same Bit Flows canvas without rebuilding the workflow from scratch.
Yes, you can connect WooCommerce to Airtable without code by using Bit Flows to trigger a workflow when a new WooCommerce order is created.
Use WooCommerce → On New Order Create when you want every new WooCommerce order to create a new Airtable record automatically.
Yes, you can filter orders by status using a Condition node or choose a WooCommerce order status trigger, depending on how specific your workflow needs to be.
You need an Airtable Personal Access Token because legacy Airtable API keys no longer work for Airtable API access.
Your Airtable bases or tables may not show if the token lacks the correct scopes, base access, or Airtable permission level.
Use Email for customer email, Phone for phone number, Number for order total, and single-line text for product name or payment method.
Yes, use Airtable Search Record first to find the existing customer or order, then pass the record ID into Airtable Update Record.
Check the Personal Access Token scopes, selected base, selected table, field mapping, required Airtable fields, and Bit Flows logs.
No, Test Run shows the output above the test area, but you need to run the full workflow to verify the result inside Bit Flows logs.
Yes, use an Iterator if your WooCommerce order has multiple line items and each product needs its own Airtable record.
Airtable is better when your team needs views, field types, filtering, relational records, and fulfillment tracking beyond a simple spreadsheet log.
Yes, but high-volume stores should monitor Bit Flows logs, WordPress hosting performance, and Airtable API limits during the first few days.
EN 
DE 
ES 
NL 
IT 
PT 
JA