Zapier Tables is Zapier's own database built for automation: each table is made of records (rows), fields (columns) and cells, and you can add records by hand or have Zaps add them for you. It's available on the Free, Professional, Team and Enterprise plans, and you start one from the Tables home with Create.
Here's the catch. Importing records doesn't trigger a Zap that uses the Zapier Tables New Record trigger. Only records you add manually, or that a Zap or an MCP client adds, set it off. So if you import a CSV of leads expecting your welcome Zap to fire for each one, nothing happens until you select them and send them to the Zap yourself, up to 10,000 records per page.
What Tables is for, and what it isn't
Zapier has three ways to hold data, and picking the right one saves you rebuilding later.
| Option | What it's for, as of October 2026 |
|---|---|
| Storage | Temporarily saving and retrieving small amounts of data from a Zap, identified by a store secret |
| Digest | Temporarily collecting small amounts of data to release later in batches |
| Tables | Small or large amounts of data, stored temporarily or permanently, that people can also view and edit |
Zapier's own suggestions for Tables are a lead management system with Zapier Forms, an onboarding tracker where new employees request access and complete paperwork, and an expense tracker you can email for reimbursement straight from the table. You can also share a table with people outside your Zapier account and give editing rights to people inside it.
The words you'll see
- Field type: the kind of data a field holds, such as text, number or date, which keeps entries consistent.
- Pending records: records that haven't been sent to a connected Zap yet.
- Table view: a filtered subset of a table you can share with people who don't need the whole thing.
- Rate limiting: Zapier slowing connected Zaps when lots of actions happen in a short time.
- Bulk edit: changing many records at once.
Building your first table
- From the Tables home, click Create and type a name.
- Click Create table, then choose Import data, a template, or Blank table.
- Click the Add field icon on the right, pick a field type, name it and fill in its settings.
- Click New record at the bottom to add rows by hand, or click a cell to edit it.
- Open Automations in the toolbar to connect a Zap to the table.
Your account-wide record usage against your plan's limits shows in the bottom-right corner of the table view. Keep an eye on it before a big import, because anything over your plan's record or field limit is ignored.
To change many rows, tick them, open the menu icon, choose Edit records, pick the field and enter the new value. Those bulk changes can't be undone, so check twice. You can also ask Zapier Copilot to edit a table in plain words, but it can't delete fields, change a field type or edit existing records.
Importing a CSV without surprises
You can import into a new table from a CSV or from certain apps, such as Google Sheets and Microsoft Excel, and Tables creates the fields for you. Or you can append a CSV to an existing table from Import records, with new rows going to the bottom. The CSV rules are strict:
- Comma-delimited only; semicolons, tabs or pipes won't work.
- UTF-8 encoded.
- Smaller than 50 MB.
- When appending, the table needs at least as many fields as the file, or some columns may not come in.
After an import, select the records, click Automate records, choose the Zaps and click Send to Zap workflows. That's the step people miss.
Triggering Zaps from a table
There are three levels. Automations and + New automation opens a Zap with the trigger already set to your table, for new or updated records. Clicking a field name and choosing + Create Zap gives you an Updated Record trigger for that field only. And a Zap built on a table view only fires for records matching that view's filters, which saves you a Filter step. Summary formulas can trigger Zaps too, whenever their value changes.
Three limits worth knowing. If you delete a field a Zap uses, the Zap stops working, although you can restore the field from Trash within 30 days. Zap steps for Tables accept dates as MM/DD/YYYY, YYYY-MM-DD or YYYY-MM-DDhh:mm:ssZ. And if you edit a Tables step in someone else's Zap, your draft saves but only the Zap owner can publish it. If your data's arriving from another tool by webhook, my guide to Zapier webhooks shows the trigger side.
Lookup tables: Tables or Formatter
A lookup table matches a value from one app to the value another app needs, such as turning a form answer into the right dropdown choice. Zapier gives you two ways to build one, and its advice is clear about which suits what.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
| Use Zapier Tables if | Use a Formatter step if |
|---|---|
| You match the same value for several apps | Your data comes as line items to process one by one |
| Teammates need access to maintain the list | You want a fallback value when there's no match |
The Formatter Lookup Table step needs a Professional plan or higher. Its Key column is case-sensitive, and if the lookup key is blank when the Zap runs, nothing is returned, not even the fallback. A quick shortcut: on any dropdown field in the Zap editor, the three dot menu offers Add lookup table step, which builds one pre-filled with the dropdown's choices.
Duplicating, deleting and recovering
Duplicate copies a table's structure, its fields, filters and hidden fields, but no records, and views aren't copied either, so you'll recreate those. Deleting a whole table from Table Settings is permanent. Deleted records and fields are different: they go to Trash and you can restore them within 30 days. A table that a Zapier Form uses can't be deleted until you remove the form's table components.
My verdict on Zapier Tables
I'd use Zapier Tables when the data mainly exists to drive automations, like a lead list that feeds follow-up Zaps or an approvals tracker, because the triggers are built in. I'd keep using a spreadsheet if people mostly analyse the data by hand. Either way, remember imports don't fire Zaps on their own. If you're new to building Zaps, start with my step-by-step guide to your first Zap.
A well-built table is often the backbone of a small team's automations. I run AI training and workshops for teams, and help businesses with AI enablement and workflow automation, so the busywork runs itself and people get time back. Most of that work is with SaaS marketing teams and small businesses. Here's how we can work together.
Frequently asked questions
Does importing a CSV into Zapier Tables trigger my Zap?
No. Imported records don't trigger a New Record Zap. Select them, click Automate records and send them to your Zaps, up to 10,000 records per page.
What file types can I import into Zapier Tables?
Comma-delimited, UTF-8 encoded CSV files smaller than 50 MB, or data from certain apps such as Google Sheets and Microsoft Excel.
Can I recover deleted records in Zapier Tables?
Yes. Deleted records and fields go to the Trash, where you can restore them within 30 days. Deleting a whole table is permanent.
Does duplicating a Zapier table copy the records?
No. It recreates the fields, filters and hidden fields, but no records, and views aren't duplicated.
Which Zapier plans include Tables?
Zapier lists Tables as available on the Free, Professional, Team and Enterprise plans.
