Skip to content
Tutorials Center
My learning

Topics

Lesson 23 of 36 ยท Tables and Interfaces

Zapier Tables Basics

Learn what Zapier Tables is, how fields, records and views work, how Zaps read and write tables, and why a table often beats a spreadsheet for automation state.

Every automation of any size needs somewhere to remember things: which orders were already processed, which lead belongs to which salesperson, what the last run's total was. Zaps themselves have no memory between runs. You can use a spreadsheet, a database app, or a built-in tool. Zapier Tables is Zapier's own no-code database, designed so Zaps can read and write it without any connection setup.

This lesson explains the concepts (tables, fields, records, views) and how Zaps work with them. The real product cannot run on this site, so menus are described in words, and the runnable code is a JavaScript stand-in that models a small table so you can practice the logic. Names and plan limits change, so check Zapier's current documentation for sizes and limits.

Tables versus spreadsheets

A table looks like a spreadsheet, but behaves like a small database.

Spreadsheet Zapier Tables
Any cell can hold anything Each field (column) has a type
Rows are positions Each record (row) has a unique record id
Formulas live in cells A formula field calculates per record
One flat view Several views with filters, sorts and hidden fields
Zaps need a connection Built-in Tables app, no login

Typed fields prevent a whole class of mistakes: you cannot save the word "soon" in a date field, and a checkbox is either checked or not.

The parts of a table

  • Table: a named collection, such as "Leads" or "Processed Orders".
  • Field: a column with a type. Common types include text (single and long), number, date, checkbox, a dropdown (single select), link to another table, URL, email, and formula. A table is created with a primary field that names each record.
  • Record: one row. It has a record id you can use to find or update it exactly.
  • View: a saved way of looking at the same data, with filters (only "New" leads), sorting, grouping and hidden columns. A view never changes the data, only what you see.

A few design tips from the start:

  1. Give every table a unique key field (order id, email) you will search by.
  2. Use a dropdown for status values (new, contacted, won) so spelling never varies.
  3. Add created_at and source fields. Future you will need them when something looks wrong.

Working with tables from a Zap

The Tables app offers these building blocks (names may be slightly different in your account, so read the list in the app):

  • Triggers: New Record, Updated Record (when a field changes), and a trigger that fires when a record enters a view. The view trigger is handy for "when a lead is marked Approved".
  • Actions: Create Record, Update Record, Find Record, Find or Create Record, Delete Record.
  • Records can also be changed by hand or by Interfaces (Interfaces: Forms and Pages).

Important behaviours to remember:

  • Find Record searches a field for a value. If nothing matches you can choose to create it if it does not exist. That one setting is how dedupe is built (Tables Lookup and Dedupe).
  • Update Record needs the record id (taken from the Find or Create step), not a field value.
  • A Zap that writes to a table can itself trigger a Zap on that table, which can create an infinite loop. Guard against it with a filter on a flag field.
flowchart LR
    A["Form submission"] --> B["Find or Create Record"]
    B --> C{"Existing?"}
    C -- "yes" --> D["Update Record"]
    C -- "no" --> E["Create Record"]
    D --> F["Send notification"]
    E --> F

Find-or-create is the heart of most table logic.

Try the idea: a tiny in-memory table

The code below is not Zapier code. It is a small table object with typed fields, create, find, update and findOrCreate, so you can see how record ids and keys behave.

JS Stand-in: a typed mini table

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The second findOrCreate for the same email returned the existing record and did not overwrite the score. That is the behaviour you want for lead capture, and the typed field refused the word "high" for a number.

Formulas and views for automation

A formula field computes a value from other fields of the same record, for example score + bonus, days since created_at, or a text such as an email subject line. Because formulas recalculate automatically, they keep logic in one place instead of repeating it in many Zaps. A view can then show "records where days_open is over 7", and a Zap can use that view as its trigger to nudge stale items. This moves complexity out of the Zap and into data, which makes Zaps shorter and easier to read.

JS Stand-in: a stale-records view

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Limits and good habits

  • Tables have plan limits on records and fields; look up the current numbers before you plan millions of rows. For large data, use a real database and call it through its API.
  • Keep sensitive data minimal: a table is shared with people who have access to your workspace (Security and Access Control).
  • Export or back up important tables regularly; deleted records may not be recoverable.
  • Name tables and fields consistently, as covered in Naming, Documentation and Change Management.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. What does an Update Record action need to know which record to change?

    Each record has a unique id. Use Find or Create to get it, then pass it to Update Record.
  2. 2. What is a view in Zapier Tables?

    Views change only what you see, never the underlying records.
  3. 3. Why can a Zap that updates a table cause an infinite loop?

    Add a filter or a flag field so the Zap ignores its own changes.

Summary

  • Zapier Tables is a typed, no-login database that Zaps can read and write.
  • Concepts: table, field (typed), record (with id), view (saved filter).
  • Core actions: Create, Find, Find or Create, Update, Delete; triggers fire on new or updated records.
  • Use formulas and views to move logic out of Zaps; guard against loops.
  • Check current plan limits and keep secrets out.

Next: Tables Lookup and Dedupe